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.
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(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
Description: text/x-vcard (285 bytes)
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2005-02-02 23:53:08|
|Subject: Re: libpq API incompatibility between 7.4 and 8.0 |
|Previous:||From: Bruce Momjian||Date: 2005-02-02 23:46:11|
|Subject: Re: libpq API incompatibility between 7.4 and 8.0|