Re: pg_dump: schema with OID XXXXX does not exist - was Concurrent CREATE TABLE/DROP SCHEMA leaves inconsistent leftovers

From: Daniel Farina <daniel(at)heroku(dot)com>
To: Nikhil Sontakke <nikkhils(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump: schema with OID XXXXX does not exist - was Concurrent CREATE TABLE/DROP SCHEMA leaves inconsistent leftovers
Date: 2011-11-11 19:08:01
Message-ID: CAAZKuFb2d1EqgLY7BV3d1hYW613q2FUOrHuqXVR12a8sT=6waQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 10, 2011 at 11:57 PM, Nikhil Sontakke <nikkhils(at)gmail(dot)com> wrote:
> Hi,
>
>>
>> But if it's deemed to be a
>> problem, I want to see a solution that's actually watertight.)
>>
>
> After Daniel's hunch about pg_dump barfing due to such leftover entries
> proving out to be true, we have one credible explanation (there might be
> other reasons too) for this long standing issue. I see some reports from as
> early as 2004 and some as latest as Feb, 2011!

The 2004 report was in version 7.3, released in 2002. So it's Very
Nearly a ten year old bug, and may very well go back further back in
time.

--
fdr

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2011-11-11 19:21:31 Re: Re: pg_dump: schema with OID XXXXX does not exist - was Concurrent CREATE TABLE/DROP SCHEMA leaves inconsistent leftovers
Previous Message Dimitri Fontaine 2011-11-11 19:04:51 Re: Multiple Extensions