Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in
От
Andrew Gierth
Тема
Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in
Дата
Msg-id
87tw6sayrv.fsf@news-spur.riddles.org.uk
Ответ на
Список
Дерево обсуждения
[COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 on non-empty relationsin Andrew Gierth <rhodiumtoad@postgresql.org>
Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in Tom Lane <tgl@sss.pgh.pa.us>
Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 onnon-empty relations in Andres Freund <andres@anarazel.de>
Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in Andrew Gierth <andrew@tao11.riddles.org.uk>
Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 on non-empty relations in Andrew Gierth <andrew@tao11.riddles.org.uk>
Re: [COMMITTERS] pgsql: Avoid having vacuum set reltuples to 0 onnon-empty relations in Vik Fearing <vik.fearing@2ndquadrant.com>
>>>>> "Tom" == Tom Lane 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 по дате отправления
От: Heikki Linnakangas
Дата:
От: Andrew Gierth
Дата: