postgresql/contrib/pg_visibility
Álvaro Herrera 01a80f0621
Revert "Allow logical replication snapshots to be database-specific"
This reverts commit 0d3dba38c7, which was determined to have
fundamental flaws.  This restricts REPACK (CONCURRENTLY) so that only
one process can run it concurrently on different tables and even on
different databases; we'll lift that restriction in another way during
the next development cycle.

Reported-by: Amit Kapila <amit.kapila16@gmail.com>
Discussion: https://postgr.es/m/CAA4eK1Jg21ODQ7fS2fvN5W_S5kDRhAP5inj3XMRQaa=s-GbYhw@mail.gmail.com
2026-05-23 21:33:19 -07:00
..
expected Fix flakiness in the pg_visibility VM-only vacuum test by using a temporary table. 2026-02-02 17:45:27 -05:00
sql Fix flakiness in the pg_visibility VM-only vacuum test by using a temporary table. 2026-02-02 17:45:27 -05:00
t Update copyright for 2026 2026-01-01 13:24:10 -05:00
.gitignore
Makefile Combine visibilitymap_set() cases in lazy_scan_prune() 2026-01-26 16:03:32 -05:00
meson.build Update copyright for 2026 2026-01-01 13:24:10 -05:00
pg_visibility--1.0--1.1.sql
pg_visibility--1.1--1.2.sql
pg_visibility--1.1.sql
pg_visibility.c Revert "Allow logical replication snapshots to be database-specific" 2026-05-23 21:33:19 -07:00
pg_visibility.control