AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Postgis versions12/18/2023 ![]() In earlier versions the bug seems to have no visible symptoms, but it's not quite clear that it could never cause a problem.įix partition pruning logic to handle asymmetric hash partition sets (Tom Lane) In PostgreSQL 13, this case reliably caused a null-pointer dereference. In installations that have enabled prepared transactions ( max_prepared_transactions > 0), it's recommended to reindex any concurrently-built indexes in case this problem occurred when they were built.Īvoid crash when a CALL or DO statement that performs a transaction rollback is executed via extended query protocol (Thomas Munro, Tom Lane) ![]() Its failure to do so meant that rows inserted by prepared transactions might be omitted from the new index, causing queries relying on the index to miss such rows. (CVE-2021-3393)įix CREATE INDEX CONCURRENTLY to wait for concurrent prepared transactions (Andrey Borodin)Īt the point where CREATE INDEX CONCURRENTLY waits for all concurrent transactions to complete so that it can see rows they inserted, it must also wait for all prepared transactions to complete, for the same reason. If an UPDATE command attempts to move a row to a different partition but finds that it violates some constraint on the new partition, and the columns in that partition are in different physical positions than in the parent table, the error message could reveal the contents of columns that the user does not have SELECT privilege on. ![]() Fix information leakage in constraint-violation error messages (Heikki Linnakangas) ![]()
0 Comments
Read More
Leave a Reply. |