Re: pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Gierth <rhodiumtoad(at)postgresql(dot)org>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in
Date: 2017-03-17 12:21:05
Message-ID: 87tw6sayrv.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Gierth 2017-03-17 13:18:55 Re: pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in
Previous Message Heikki Linnakangas 2017-03-17 09:37:03 pgsql: Allow plaintext 'password' authentication when user has a SCRAM