chris.gamble@CPBINC.com writes:
> My questions is, when does the memory
> storage used for this currval get released and what triggers its
> release?
It's not released until your session exits.
> If
> it is never released, does that cause the process to consume excessive
> memory after several inserts across multiple tables?
Since the storage involved is just a few bytes for each distinct
sequence object that you've nextval'd in the current session, I doubt
that you need to worry. Certainly doing multiple inserts into a single
table isn't going to bloat your memory consumption, because you're
touching only one sequence.
regards, tom lane