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

From Bossart, Nathan
Subject Re: pgsql: When VACUUM or ANALYZE skips a concurrently dropped table,log i
Date
Msg-id E1E33F47-1B82-47EF-BA48-BBF2421AE3DF@amazon.com
Whole thread Raw
In response to Re: pgsql: When VACUUM or ANALYZE skips a concurrently dropped table,log i  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: pgsql: When VACUUM or ANALYZE skips a concurrently dropped table,log i
List pgsql-hackers
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.

Nathan


Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pgsql: When VACUUM or ANALYZE skips a concurrently dropped table,log i
Next
From: Craig Ringer
Date:
Subject: Re: Postgres with pthread