| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | cgg007(at)yahoo(dot)com |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: undefine currval() |
| Date: | 2003-09-08 21:33:02 |
| Message-ID: | 3633.1063056782@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
Chris Gamache <cgg007(at)yahoo(dot)com> writes:
> One (theoretical) workaround would be to issue some sort of command to the
> back-end database to wipe all values of currval() when a "new" connection is
> made. I've done some digging in the system tables and source code, and can't
> find an obvious solution.
The state involved is in a linked list kept by commands/sequence.c.
Such a command would not be difficult to implement, if you could get
agreement on the syntax to use.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gaetano Mendola | 2003-09-08 21:38:27 | Re: constraint modification on todo list |
| Previous Message | Andrew Dunstan | 2003-09-08 21:31:33 | Re: plpgsql doesn't coerce boolean expressions to boolean |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-09-08 22:41:00 | Re: undefine currval() |
| Previous Message | Andrew Dunstan | 2003-09-08 21:31:33 | Re: plpgsql doesn't coerce boolean expressions to boolean |