Re: Explicite typecasting of functions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: Andreas Tille <tillea(at)rki(dot)de>, PostgreSQL SQL <pgsql-sql(at)postgresql(dot)org>
Subject: Re: Explicite typecasting of functions
Date: 2002-08-14 15:20:09
Message-ID: 8505.1029338409@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Richard Huxton <dev(at)archonet(dot)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

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Wei Weng 2002-08-14 15:29:26 Re: concurrent connections is worse than serialization?
Previous Message Richard Huxton 2002-08-14 14:49:57 Re: concurrent connections is worse than serialization?