summaryrefslogtreecommitdiff
path: root/databases/postgresql84-pgcrypto
diff options
context:
space:
mode:
authoradam <adam@pkgsrc.org>2011-12-02 14:25:09 +0000
committeradam <adam@pkgsrc.org>2011-12-02 14:25:09 +0000
commit14d94040144c7cc562f54efdbc0b4ee9c257b312 (patch)
tree6dde161db929ee4e2a99383ae5131fd13c3d15a3 /databases/postgresql84-pgcrypto
parentf24775d7a7b1959c0f99aad3bcc72ccc2723e119 (diff)
downloadpkgsrc-14d94040144c7cc562f54efdbc0b4ee9c257b312.tar.gz
Changes 5.1.60:
* Upgrading from an Advanced GPL RPM package to an Advanced RPM package did not work. Now on Linux it is possible to use rpm -U to replace any installed MySQL product by any other of the same release family. It is not necessary to remove the old produce with rpm -e first. * MEMORY table creation time is now available in the CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table and the Create_time column of SHOW TABLE STATUS output. Bugs Fixed * Important Change: InnoDB Storage Engine: Data from BLOB columns could be lost if the server crashed at a precise moment when other columns were being updated in an InnoDB table. * InnoDB Storage Engine: This fix improves the performance of instrumentation code for InnoDB buffer pool operations. * InnoDB Storage Engine: Lookups using secondary indexes could give incorrect matches under a specific set of conditions. The conditions involve an index defined on a column prefix, for a BLOB or other long column stored outside the index page, with a table using the Barracuda file format. * InnoDB Storage Engine: This fix corrects cases where the MySQL server could hang or abort with a long semaphore wait message. (This is a different issue than when these symptoms occurred during a CHECK TABLE statement.) * Replication: Issuing the following statements, in the order shown, could cause a deadlock between the user thread and I/O thread. * more...
Diffstat (limited to 'databases/postgresql84-pgcrypto')
0 files changed, 0 insertions, 0 deletions