Re: New setval() call - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: New setval() call
Date
Msg-id 200102102334.SAA20214@candle.pha.pa.us
Whole thread Raw
In response to Re: New setval() call  (Philip Warner <pjw@rhyme.com.au>)
Responses Re: New setval() call
List pgsql-hackers
> At 12:23 10/02/01 -0500, Bruce Momjian wrote:
> >I am inclinded to remove this open item:
> >
> >    New SQL function setval(seq,val,bool) for use in pg_dump (Philip)
> >
> >The use of the 3rd parameter, 'iscalled', while used by pg_dump, is not
> >of general use, so we probably don't need to document it.  Is this valid?
> >
> >Info on the new param is:
> 
> Fine with me; I think your recollection is correct - but it would be worth
> putting a description *somewhere*. Do we have an internals doc of any kind?
> Something that describes interfaces etc that are not guaranteed to remain
> static or supported?

Can you give me a few lines to put in sequence.c?  There isn't even
anything in there!

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Philip Warner
Date:
Subject: Re: New setval() call
Next
From: Bruce Momjian
Date:
Subject: Re: [ODBC] RE: [PATCHES] Fix for ODBC close