While that works in normal use-cases, it can result in an unexpected failure for clients running as root, and perhaps in other cases.Įnsure ecpg reports server connection loss sanely (Tom Lane) But we should not have also copied the server's file-ownership check. In the previous minor releases, we copied the server's permission checking rules for SSL private key files into libpq. Remove misguided SSL key file ownership check in libpq (Tom Lane) Previously, although extensions could choose to create such settings, some code paths would crash while processing them. Such cases could result in harmless warning messages.Īllow custom server parameters to have short descriptions that are NULL (Steve Chavez) Prevent open-file leak when reading an invalid timezone abbreviation file (Kyotaro Horiguchi) Fix that by ensuring we send keepalive messages periodically in such situations. If a large transaction on the primary server sends no data to the standby (perhaps because no table it changes is published), it was possible for the standby to timeout. ![]() Prevent triggering of standby's wal_receiver_timeout during logical replication of large transactions (Wang Wei, Amit Kapila) Previously, when the restartpoint completed it could incorrectly update the last-checkpoint fields of the control file, potentially leading to PANIC and failure to restart if the server crashes before the next normal checkpoint completes. If CREATE OPERATOR CLASS results in the implicit creation of an operator family, that object was not reported to event triggers that should capture such events.įix control file updates made when a restartpoint is running during promotion of a standby server (Kyotaro Horiguchi) Report implicitly-created operator families to event triggers (Masahiko Sawada) ![]() Previously, this auto-generated alias was always hidden but there are corner cases where doing so results in a non-restorable view or rule definition. When decompiling a view or rule, show a SELECT output column's AS "?column?" alias clause if it could be referenced elsewhere (Tom Lane) This mistake could lead to false complaints of invalidly-encoded input data.Īvoid crashing if too many column aliases are attached to an XMLTABLE or JSON_TABLE construct (Álvaro Herrera) Prevent pg_stat_get_subscription() from possibly returning an extra row containing garbage values (Kuntal Ghosh)įix COPY FROM's error checking in the case where the database encoding is SQL_ASCII while the client's encoding is a multi-byte encoding (Heikki Linnakangas) This mistake could lead to Memoize being used when it isn't really the best plan, or to very long executor startup times due to initializing an overly-large hash table for a Memoize node.įix queries in which a “ whole-row variable” references the result of a function that returns a domain over composite type (Tom Lane)įix “ variable not found in subplan target list” planner error when pulling up a sub- SELECT that's referenced in a GROUPING function (Richard Guo) Throw a runtime error instead.įix incorrect cost estimates for Memoize plans (David Rowley) Memoize could crash if a data type's equality or hash functions gave inconsistent results across different calls. Harden Memoize plan node against non-deterministic equality functions (David Rowley) (Alternatively, rebuild them without CONCURRENTLY.) It is recommended that any indexes made with the CONCURRENTLY option be rebuilt after installing this update. ![]() CONCURRENTLY to sometimes miss indexing rows that were updated during the index build. ![]() Prevent possible corruption of indexes created or rebuilt with the CONCURRENTLY option (Álvaro Herrera)Īn optimization added in v14 caused CREATE INDEX.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |