- Small improvement in CegoDbThreadPool. For a better db thread
load value calculation, the request queue is no longer locked while
waiting for incoming requests. Instead the QUEUEDELAY parameter has been
increased to a default value of 200 msec to reduce db thread cpu
load while idle. Now the db thread has a good chance to report
idle time to the db thread pool.
Submitted by: Bjoern Lemke <lemke@lemke-it.com>
When feasible do this by adding -D_WANT_SEMUN to CFLAGS or CXXFLAGS.
Where this fails due to ports not honoring C*FLAGS, patch using
__FreeBSD_version to enable the definition.
PR: 224300, 224443 (exp-run)
Approved by: portmgr (antoine)
Exp-run: antoine
Sponsored by: DARPA, AFRL
Differential Revision: https://reviews.freebsd.org/D14137
ibase is Firebird, which only builds on i386 and amd64. This patch
squashes the ibase plugin for Qt4.
PR: 216943
Submitted by: linimon
Reported by: linimon
Approved by: tcberner (mentor)
Differential Revision: https://reviews.freebsd.org/D14326
The PostgreSQL Global Development Group has released an update to all supported
versions of the PostgreSQL database system, including 10.3, 9.6.8, 9.5.12,
9.4.17, and 9.3.22.
The purpose of this release is to address CVE-2018-1058, which describes how a
user can create like-named objects in different schemas that can change the
behavior of other users' queries and cause unexpected or malicious behavior,
also known as a "trojan-horse" attack. Most of this release centers around added
documentation that describes the issue and how to take steps to mitigate the
impact on PostgreSQL databases.
We strongly encourage all of our users to please visit
https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058:_Protect_Your_Search_Path
for a detailed explanation of CVE-2018-1058 and how to protect your PostgreSQL
installations.
After evaluating the documentation for CVE-2018-1058, a database administrator
may need to take follow up steps on their PostgreSQL installations to ensure
they are protected from exploitation.
Security: CVE-2018-1058
databases/cegobridge: update 1.3.0 -> 1.4.0
cego:
- Fix in CegoTableManager::updateTuple, while setting up expression
list, field list array must be setup BEFORE block ist set, since
field list is needed by block setup ( in case of subqueries for
prepare )
cegobridge:
- Adaptions for cego-2.39
Submitted by: Bjoern Lemke <lemke@lemke-it.com>
- Introduced table locking statements to set an explicit lock on a
table ( e.g. for update synchronisation ). This feature replaces
the "set update sync on/off" command
- Trigger implementation basically completed
- Fix in CegoQueryHelper::encodeFVL, for blob/clob values lists,
the corresponding index variables ( blobidx/clobidx ) have not been
increaed while encoding lob data. This might lead to invalid results
and seg faults in case of multiple lobs values in one insert/update
operation.
Submitted by: Bjoern Lemke <lemke@lemke-it.com>
- For heavy update operations on tables with btrees using embedding
transactions, duplicate btree errors may occur. This is caused
by not checking corresponding tuple states. To solve this problem,
the following fixes have been done :
o Fix in CegoTableManager::checkBTreeIntegrity : The tuple state for
found entries has to be checked if state = COMMITTED
o Fix in CegoBTreeNode:checkForAffected ( was checkForDeleted before ) :
The tuple state has already checked for state
INSERTED if tid != dataTid
Submitted by: Bjoern Lemke <lemke@lemke-it.com>
