Re: pgsql: When VACUUM or ANALYZE skips a concurrently dropped table,log i - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pgsql: When VACUUM or ANALYZE skips a concurrently dropped table,log i
Date
Msg-id CA+TgmobhT8XcHfjK_K0QxtjXxdNqETinbu7t3qkvgzpz6fCaeQ@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: When VACUUM or ANALYZE skips a concurrently dropped table,log i  ("Bossart, Nathan" <bossartn@amazon.com>)
List pgsql-hackers
On Wed, Dec 6, 2017 at 9:42 PM, Bossart, Nathan <bossartn@amazon.com> wrote:
> On 12/6/17, 8:25 PM, "Robert Haas" <robertmhaas@gmail.com> wrote:
>> Please give me a little time to see if I can speed up this test enough
>> to fix this problem.  If that doesn't work out, then we can rip this
>> out.
>
> Just in case it got missed earlier, here’s a patch that speeds it
> up enough to pass with CLOBBER_CACHE_ALWAYS enabled.  Instead of
> doing database-wide operations, it just uses a partitioned table.

Yeah, that looks like a reasonable approach to try.  Committed, thanks.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Speeding up pg_upgrade
Next
From: Justin Pryzby
Date:
Subject: Re: Speeding up pg_upgrade