Re: Proposed patch for sequence-renaming problems - Mailing list pgsql-patches

From Tom Lane
Subject Re: Proposed patch for sequence-renaming problems
Date
Msg-id 8731.1128182112@sss.pgh.pa.us
Whole thread Raw
In response to Re: Proposed patch for sequence-renaming problems  (Gavin Sherry <swm@linuxworld.com.au>)
List pgsql-patches
Gavin Sherry <swm@linuxworld.com.au> writes:
> Well, AFAICT, the only part of the spec we cannot implement is what you
> quote above. Therefore, why can't we support NEXT VALUE FOR seqname and
> reject table creation/alteration which would add more than one reference
> to the same sequence.

And how are you going to determine whether a query (not a table
definition) contains more than one NEXT VALUE FOR the same sequence?
Bear in mind some of them could be hidden down inside views or
functions.

            regards, tom lane

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Making pgxs builds work with a relocated installation
Next
From: "Dave Page"
Date:
Subject: Re: Making pgxs builds work with a relocated installation