Re: pg_dump future problem. - Mailing list pgsql-hackers

From Philip Warner
Subject Re: pg_dump future problem.
Date
Msg-id 5.1.0.14.0.20030506013859.02ab2750@mail.rhyme.com.au
Whole thread Raw
In response to Re: pg_dump future problem.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
At 11:22 AM 5/05/2003 -0400, Tom Lane wrote:
>But the proposed "nicer interface" *introduces* a bug, namely the
>inability to preserve is_called, which is exactly the pg_dump bug
>that 3-parameter setval was invented to fix.

No, I don't want to remove the setval functions from general sequences. I 
just want to use existing restrictions on the SERIAL data type: by 
definition they start at 0, increase by 1, and are intX. We can ignore the 
current is_called flag and set the min value or is_called flag in such a 
way as to get the desired next value.


----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.B.N. 75 008 659 498)          |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 03 5330 3172          |                 ___________ |
Http://www.rhyme.com.au          |                /           \|                                 |    --________--
PGP key available upon request,  |  /
and from pgp5.ai.mit.edu:11371   |/



pgsql-hackers by date:

Previous
From: Philip Warner
Date:
Subject: Re: Why are triggers semi-deferred?
Next
From: Stephan Szabo
Date:
Subject: Re: Why are triggers semi-deferred?