Fix autovacuum for shared relations
The table-skipping logic in autovacuum would fail to consider that
multiple workers could be processing the same shared catalog in
different databases. This normally wouldn't be a problem: firstly
because autovacuum workers not for wraparound would simply ignore tables
in which they cannot acquire lock, and secondly because most of the time
these tables are small enough that even if multiple for-wraparound
workers are stuck in the same catalog, they would be over pretty
quickly. But in cases where the catalogs are severely bloated it could
become a problem.
Backpatch all the way back, because the problem has been there since the
beginning.
Reported by Ondřej Světlík
Discussion: https://www.postgresql.org/message-id/572B63B1.3030603%40flexibee.euhttps://www.postgresql.org/message-id/572A1072.5080308%40flexibee.eu
Branch
------
REL9_3_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/92ebe509e381002f62faeeeb9007723409725323
Modified Files
--------------
src/backend/postmaster/autovacuum.c | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
