Re: NEXT VALUE FOR...

From: Rod Taylor <pg(at)rbt(dot)ca>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: NEXT VALUE FOR...
Date: 2004-05-07 19:18:04
Message-ID: 1083957483.28644.19.camel@jester
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

> How we do what the spec wants isn't entirely clear, but maybe we could
> link all the supposed-to-track-each-other occurrences of NEXT VALUE FOR
> late in the planning stage or during executor startup, somewhat like
> what happens with aggregate functions.

Isn't there a statement level memory location that we could shove a
boolean variable? Then let the executor determine whether to call todays
version of nextval() or currval() based on that?

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-05-07 20:01:48 Re: NEXT VALUE FOR...
Previous Message Tom Lane 2004-05-07 19:16:00 Re: NEXT VALUE FOR...