Re: pg_dump bug in 7.3.9 with sequences - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: pg_dump bug in 7.3.9 with sequences
Date
Msg-id 42016727.3020107@commandprompt.com
Whole thread Raw
In response to Re: pg_dump bug in 7.3.9 with sequences  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
Responses Re: pg_dump bug in 7.3.9 with sequences  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
Re: pg_dump bug in 7.3.9 with sequences  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Alvaro Herrera wrote:

>On Wed, Feb 02, 2005 at 01:54:48PM -0800, Joshua D. Drake wrote:
>
>
>
>>It is not pilot error if PostgreSQL allows it. There is
>>nothing "illegal" about the above commands in their execution.
>>The pg_dump application should recognize that the object has
>>changed and react accordingly.
>>
>>
>
>ISTM this is a bug, but it's not clear to me what is the solution.
>I can think of two:
>
>1. Changing the default is forbidden
>2. When the default is changed, the dependency on the sequence is
>dropped, and the sequence itself is dropped.
>
>
3. When the default is changed, the dependency is updated
to reflect the new sequence. The old sequence is left intact
as an independent object.

Sincerely,

Joshua D. Drake




>Which one do you think is best?  Why?  (I'd say "less bad" instead of
>"best", but I'm not sure if that's a correct choice of words.)
>
>
>


--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL


Attachment

pgsql-hackers by date:

Previous
From: John Hansen
Date:
Subject: unicode upper/lower functions
Next
From: "Greg Sabino Mullane"
Date:
Subject: Re: [NOVICE] Last ID Problem