Mike Nolan <nolan@gw.tssi.com> writes:
> It sound to me like there's the potential for a second web program sharing
> the persistent connection to do something in between the nextval and
> the currval.
"Don't do that then."
Your code should hang on to the same connection for as long as it
needs to rely on the correct value of currval().
> Is currval for each process maintained at the front end (e.g., the PHP or
> psql connection) or at the back end? If the latter, isn't there always
> the potential for memory overflows or other high-demand situations causing
> the pairing of nextval/currval to get corrupted or lost, in which case
> RELYING upon it for the last key value could be a source of problems.
How, exactly, would this happen? Is this worry based on an analysis
of the source code, or just speculation?
-Doug