Re: Explicite typecasting of functions - Mailing list pgsql-sql

From Tom Lane
Subject Re: Explicite typecasting of functions
Date
Msg-id 8505.1029338409@sss.pgh.pa.us
Whole thread Raw
In response to Re: Explicite typecasting of functions  (Richard Huxton <dev@archonet.com>)
Responses Re: Explicite typecasting of functions  (Andreas Tille <tillea@rki.de>)
Re: Explicite typecasting of functions  (Andreas Tille <tillea@rki.de>)
List pgsql-sql
Richard Huxton <dev@archonet.com> writes:
> On Wednesday 14 Aug 2002 10:30 am, Andreas Tille wrote:
>> Any hint to solve this kind of chicken-egg-problem?

> Your solution is not safe anyway - you could end up with two processes trying
> to insert the next value.

I concur with Richard that Andreas needs to solve a different problem,
but just for the record, the way you could do it is
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.
        regards, tom lane


pgsql-sql by date:

Previous
From: Richard Huxton
Date:
Subject: Re: concurrent connections is worse than serialization?
Next
From: Wei Weng
Date:
Subject: Re: concurrent connections is worse than serialization?