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. į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.
It's recommended to reindex any GiST index that's been subject to concurrent insertions.
#Pro tools 12.7 unrecoverable error update
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 kommentar(er)
