- Fix in CegoTableManager::deleteDataTable, pBlock has to be checked
for null value, otherwise crash recovery might crash. ( bug came
with 2.39.0 to check for pBlock->getTriggerValueList )
- Some clob related fixes in CegoQueryHelper::decodeNativeFVL /
decodeFVL relevant for recovery handling
- Fix in CegoRecoveryManager::recoverCurrentTransactionLog for the
INSERT case. For the blob/clob handling, the lobREf values have not
been set up correctly. This might lead to problems for table recovery
with more than one lob row ( e.g. table t1 ( a blob , b clob )
Submitted by: Bjoern Lemke <lemke@lemke-it.com>
Ports using USES=php:phpize, php:ext, php:zend, and php:pecl are now
flavored. They will automatically get flavors (php56, php70, php71, php72)
depending of the versions they support (set with IGNORE_WITH_PHP). As a
consequence, ports using USES=pear and USES=horde are also flavored.
PR: 226242
Submitted by: mat
Exp-run by: antoine
Approved by: portmgr
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D14208
- Bug fix in CegoAction::reallocateStringBuf, in the memcpy call,
just the previous stringBufLen has to be copied ( _stringBufLen -
MAXSTRINGLEN ). This bug might lead to seg fault in case of large
parser input ( e.g. clob strings )
- In CegoQuery for insert and insert-by-select case, allocated blob
and clob data ( by CegoQueryHelper::prepareFieldValue ) is cleaned
now if any exception occurs
Submitted by: Bjoern Lemke <lemke@lemke-it.com>
Port changes:
* Changed to DISTVERSION
* Use MAKE_ENV to unbreak it
* Added SSP_UNSAFE because otherwise it doesn't like -fstack-protector
PR: 226378
Submitted by: Andreas Andersson <a.andersson.thn@gmail.com> (maintainer)
Approved by: tcberner (mentor, implicit)
- Small bug fix in CegoDistManager, which came up with version
2.39.0. In method deleteLocalDataTable, the variable delCount was
declared two times, which lead to a result of 0 tuples deleted in
any case
Submitted by: Bjoern Lemke <lemke@lemke-it.com>
In file included from /wrkdirs/usr/ports/databases/php5-pdo_cassandra/work/php-pdo_cassandra-7debd5b/cassandra_driver.cpp:18:
./php_pdo_cassandra_int.hpp:89:33: error: implicit instantiation of undefined template 'boost::shared_ptr<apache::thrift::transport::TSocketPool>'
boost::shared_ptr<TSocketPool> socket;
^
/usr/local/include/boost/exception/exception.hpp:19:44: note: template is declared here
namespace boost { template <class T> class shared_ptr; };
^
In file included from /wrkdirs/usr/ports/databases/php5-pdo_cassandra/work/php-pdo_cassandra-7debd5b/cassandra_driver.cpp:18:
./php_pdo_cassandra_int.hpp:90:38: error: implicit instantiation of undefined template 'boost::shared_ptr<apache::thrift::transport::TFramedTransport>'
boost::shared_ptr<TFramedTransport> transport;
^
/usr/local/include/boost/exception/exception.hpp:19:44: note: template is declared here
namespace boost { template <class T> class shared_ptr; };
^
In file included from /wrkdirs/usr/ports/databases/php5-pdo_cassandra/work/php-pdo_cassandra-7debd5b/cassandra_driver.cpp:18:
./php_pdo_cassandra_int.hpp:91:31: error: implicit instantiation of undefined template 'boost::shared_ptr<apache::thrift::protocol::TProtocol>'
boost::shared_ptr<TProtocol> protocol;
^
/usr/local/include/boost/exception/exception.hpp:19:44: note: template is declared here
namespace boost { template <class T> class shared_ptr; };
^
In file included from /wrkdirs/usr/ports/databases/php5-pdo_cassandra/work/php-pdo_cassandra-7debd5b/cassandra_driver.cpp:18:
./php_pdo_cassandra_int.hpp:92:37: error: implicit instantiation of undefined template 'boost::shared_ptr<org::apache::cassandra::CassandraClient>'
boost::shared_ptr<CassandraClient> client;
^
/usr/local/include/boost/exception/exception.hpp:19:44: note: template is declared here
namespace boost { template <class T> class shared_ptr; };
^
In file included from /wrkdirs/usr/ports/databases/php5-pdo_cassandra/work/php-pdo_cassandra-7debd5b/cassandra_driver.cpp:18:
./php_pdo_cassandra_int.hpp:109:31: error: implicit instantiation of undefined template 'boost::shared_ptr<org::apache::cassandra::CqlResult>'
boost::shared_ptr<CqlResult> result;
^
/usr/local/include/boost/exception/exception.hpp:19:44: note: template is declared here
namespace boost { template <class T> class shared_ptr; };
^
Reported by: pkg-fallout
- 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
