Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in - Mailing list pgsql-committers

From Andrew Gierth
Subject Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in
Date
Msg-id 87tw6sayrv.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-committers
>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:

 Tom> Hm, buildfarm results suggest this test is not entirely stable:

I see it and will work on it.

 Tom> I have not looked very closely, but I'm suspicious that the test
 Tom> case depends on no autovacuum transactions running concurrently
 Tom> with it.  Disabling autovac on the table itself is not enough to
 Tom> control whether global xmin is being held back by some other
 Tom> autovac transaction somewhere.

Aren't vacuum transactions ignored for that? vacuum_set_xid_limits is
certainly passing ignoreVacuum=true to GetOldestXmin.

--
Andrew.


pgsql-committers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: [COMMITTERS] pgsql: Allow plaintext 'password' authentication when user has aSCRAM
Next
From: Andrew Gierth
Date:
Subject: Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in