mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-09-07 10:09:21 +02:00
ea9125304d
Parallel pg_restore has always supposed that ACL items for different objects are independent and can be restored in parallel without conflicts. However, there is one case where this fails: because REVOKE on a table is defined to also revoke the privilege(s) at column level, we can't restore per-column ACLs till after we restore any table-level privileges on their table. Failure to honor this restriction can lead to "tuple concurrently updated" errors during parallel restore, or even to the per-column ACLs silently disappearing because the table-level REVOKE is executed afterwards. To fix, add a dependency from each column-level ACL item to its table's ACL item, if there is one. Note that this doesn't fix the hazard for pre-existing archive files, only for ones made with a corrected pg_dump. Given that the bug's been there quite awhile without field reports, I think this is acceptable. This requires changing the API of pg_dump's dumpACL() function. To keep its argument list from getting even longer, I removed the "CatalogId objCatId" argument, which has been unused for ages. Per report from Justin Pryzby. Back-patch to all supported branches. Discussion: https://postgr.es/m/20200706050129.GW4107@telsasoft.com |
||
---|---|---|
.. | ||
initdb | ||
pg_archivecleanup | ||
pg_basebackup | ||
pg_checksums | ||
pg_config | ||
pg_controldata | ||
pg_ctl | ||
pg_dump | ||
pg_resetwal | ||
pg_rewind | ||
pg_test_fsync | ||
pg_test_timing | ||
pg_upgrade | ||
pg_verifybackup | ||
pg_waldump | ||
pgbench | ||
pgevent | ||
psql | ||
scripts | ||
Makefile |