Postgres Pro
Downloads
Home   >   mailing lists

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

From Bossart, Nathan
Subject Re: pgsql: When VACUUM or ANALYZE skips a concurrently dropped table,log i
Date
Msg-id 0C15CC12-F34A-4CC1-B209-9D6C92291F41@amazon.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-committers
Tree view 
On 12/6/17, 1:23 PM, "Bossart, Nathan" <bossartn@amazon.com> wrote:
> Perhaps this could be fixed by modifying the database-wide cases to
> use partitioned tables instead.  The individual partitions will not
> have RangeVars specified, so it would cover the case when logging
> should be skipped.

This fixed the problem for me.  I've attached a patch.

Nathan
Attachment

pgsql-committers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] [COMMITTERS] pgsql: Fix freezing of a dead HOT-updatedtuple
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple