Re: New setval() call

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: New setval() call
Date: 2001-02-10 23:32:00
Message-ID: 3.0.5.32.20010211103200.02f9c100@mail.rhyme.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-02-10 23:34:20 Re: New setval() call
Previous Message Dave Page 2001-02-10 23:15:18 RE: [PATCHES] Fix for ODBC close