Re: pgsql: Avoid creation of the free space map for small heap relations.

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Amit Kapila <akapila(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, John Naylor <john(dot)naylor(at)2ndquadrant(dot)com>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Avoid creation of the free space map for small heap relations.
Date: 2019-01-28 04:55:06
Message-ID: 877eepjt3p.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

>>>>> "Amit" == Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> writes:

Amit> One possibility is that autovacuum has triggered to perform
Amit> truncation of some other relation (remove pages at the end) which
Amit> doesn't allow the FSM test to remove the rows/perform truncation
Amit> and thus let to the failure. Can there be anything else which can
Amit> start a transaction when a regression test is running? Still
Amit> thinking, but inputs are welcome.

I've bumped into issues (cf. commit 64ae420b2) with regression tests of
this kind caused by concurrent (auto-)ANALYZE (not VACUUM); VACUUM's
snapshot is ignored for testing for whether row versions can be removed,
but ANALYZE's is not.

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Amit Kapila 2019-01-28 05:37:11 Re: pgsql: Avoid creation of the free space map for small heap relations.
Previous Message Amit Kapila 2019-01-28 04:17:00 Re: pgsql: Avoid creation of the free space map for small heap relations.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuro Yamada 2019-01-28 05:18:25 Re: Tab completion for ALTER INDEX|TABLE ALTER COLUMN SET STATISTICS
Previous Message Amit Kapila 2019-01-28 04:53:26 Re: WIP: Avoid creation of the free space map for small tables