Re: pg_dump and sequences - RFC

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump and sequences - RFC
Date: 2000-09-28 16:25:24
Message-ID: 3.0.5.32.20000929022524.0414c210@mail.rhyme.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 11:17 28/09/00 -0400, Tom Lane wrote:
>
>Hmm, good point. There isn't any real easy way to refer to a sequence
>by OID --- the sequence functions only accept names --- but I suppose
>someone out there might be doing something with sequence OIDs.

So long as the backend & metadata don't rely on the OID, then it's 99.9%
safe, I'd guess. I'd be happy to go with this, and do a function later
if/when necessary (see below).

>Perhaps the real answer is to extend the set of sequence functions so
>that it's possible to set/clear is_called directly. Perhaps a variant
>setval() with an additional, boolean argument?

This would be something I'd like to do as a learning exercise. However,
aren't we 2 days from beta? Is this enough time to learn how to add a
function to the backend?

----------------------------------------------------------------
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 Jerome Raupach 2000-09-28 16:30:24 pgaccess
Previous Message Philip Warner 2000-09-28 16:06:50 Re: pg_dump and sequences - RFC