Content-Type: text/plain;
  charset="iso-8859-1"
From: Richard Huxton <dev@archonet.com>
Organization: Archonet Ltd
To: Andreas Tille <tillea@rki.de>,
	PostgreSQL SQL <pgsql-sql@postgresql.org>
Subject: Re: Explicite typecasting of functions
Date: Thu, 15 Aug 2002 09:43:53 +0100
User-Agent: KMail/1.4.1
References: 
 <Pine.LNX.4.44.0208150908430.8253-100000@wr-linux02.rki.ivbb.bund.de>
In-Reply-To: 
 <Pine.LNX.4.44.0208150908430.8253-100000@wr-linux02.rki.ivbb.bund.de>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200208150943.54761.dev@archonet.com>

On Thursday 15 Aug 2002 8:13 am, Andreas Tille wrote:
> On Wed, 14 Aug 2002, Tom Lane wrote:
> > 	CREATE TABLE without mentioning the default
> > 	CREATE FUNCTION
> > 	ALTER TABLE ... SET DEFAULT
> >
> > Note however that pg_dump is not bright enough to deduce that you did
> > this.  It will dump the table definition first, with the DEFAULT clause,
> > and so you'll have to do manual surgery on the dump file if you ever
> > need to reload.
>
> Hmmm, the original problem I wanted to solve using this function is that
> pg_dump is not bright enough to store sequences.

Eh? If you run a pg_dump on your database you should get something like:

CREATE SEQUENCE "bar_a_seq" start 1 increment 1 maxvalue 922337203685477580=
7=20
minvalue 1 cache 1;

CREATE TABLE "bar" (
        "a" integer DEFAULT nextval('"bar_a_seq"'::text) NOT NULL,
        "b" integer
);

... data then follows...

-- Name: bar_a_seq Type: SEQUENCE SET Owner: richardh
SELECT setval ('"bar_a_seq"', 3, true);

It's that last bit that sets the value of the sequence. Now AFAIK pg_dump's=
=20
been like that pretty much forever.

Note - if you only pg_dump the table, you won't get the sequence, you need =
to=20
dump the whole DB and grep away the bits you don't want.

- Richard Huxton