Re: Proposed p.tch for sequence-renaming problems - Mailing list pgsql-patches

From Tom Lane
Subject Re: Proposed p.tch for sequence-renaming problems
Date
Msg-id 1726.1127880859@sss.pgh.pa.us
Whole thread Raw
In response to Re: Proposed p.tch for sequence-renaming problems  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-patches
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Why did you rename the C function nextval() to nextval_text()?

I did that deliberately to make sure I'd catch all the dependencies.
If you like we can argue about whether to undo that aspect of the
patch --- it's surely not very critical --- but my vision of the future
path of development is that the text variant will go away entirely.
So I didn't like the idea of having "nextval" and "nextval_oid";
seems like that gives pride of place to the wrong thing.

> As an unrelated note, since we are going to force an initdb for the next
> beta, it would be nice to include the 64 bit parameter to pg_control ...

See other thread.

            regards, tom lane

pgsql-patches by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Proposed p.tch for sequence-renaming problems
Next
From: "Dave Page"
Date:
Subject: Re: [HACKERS] Making pgxs builds work with a relocated installation