#Postgresql 9.2 install dblink archive#
#Postgresql 9.2 install dblink code#

Under the right circumstances, DELETE RETURNING could attempt to fetch data from a shared buffer that the current process no longer has any pin on. Fix race condition in DELETE RETURNING (Tom Lane). Avoid deleting not-yet-archived WAL files during crash recovery (Heikki Linnakangas, Fujii Masao)

This is needed to ensure that the database is consistent in certain scenarios, such as initializing a standby server with a filesystem snapshot from a running server.

#Postgresql 9.2 install dblink archive#

Ensure we do crash recovery before entering archive recovery, if the database was not stopped cleanly and a nf file is present (Heikki Linnakangas, Kyotaro Horiguchi, Mitsumasa Kondo). This bug could result in 'incorrect local pin count' errors during replay, making recovery impossible.

Fix buffer leak in WAL replay (Heikki Linnakangas).

#Postgresql 9.2 install dblink code#

Index scans on GiST indexes on point columns would sometimes yield results different from a sequential scan, because gist_point_consistent disagreed with the underlying operator code about whether to do comparisons exactly or fuzzily.

Fix gist_point_consistent to handle fuzziness consistently (Alexander Korotkov) Users are advised to REINDEX multi-column GiST indexes after installing this update. These errors could result in inconsistent indexes in which some keys that are present would not be found by searches, and also in indexes that are unnecessarily inefficient to search. Fix bugs in GiST page splitting code for multi-column indexes (Tom Lane). Users are advised to REINDEX such indexes after installing this update. These errors could result in inconsistent indexes in which some keys that are present would not be found by searches, and also in useless index bloat. Fix erroneous range-union and penalty logic in GiST indexes that use contrib/btree_gist for variable-width data types, that is text, bytea, bit, and numeric columns (Tom Lane). After installing this update, users should REINDEX any GiST indexes on box, polygon, circle, or point columns, since all of these use gist_box_same. The core geometric types perform comparisons using 'fuzzy' equality, but gist_box_same must do exact comparisons, else GiST indexes using it might become inconsistent. Fix GiST indexes to not use 'fuzzy' geometric comparisons when it's not appropriate to do so (Alexander Korotkov). An unprivileged database user could exploit this mistake to call pg_start_backup() or pg_stop_backup(), thus possibly interfering with creation of routine backups. Make REPLICATION privilege checks test current user not authenticated user (Noah Misch) The risk is only significant when the postmaster is configured with ssl = on but most connections don't use SSL encryption. This avoids a scenario wherein random numbers generated by contrib/pgcrypto functions might be relatively easy for another database user to guess. Reset OpenSSL randomness state in each postmaster child process (Marko Kreen). A connection request containing a database name that begins with '-' could be crafted to damage or destroy files within the server's data directory, even if the request is eventually rejected. Fix insecure parsing of server command-line switches (Mitsumasa Kondo, Kyotaro Horiguchi)