| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rod Taylor <rbt(at)rbt(dot)ca> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Sequence Cleanup |
| Date: | 2002-12-09 21:19:54 |
| Message-ID: | 19692.1039468794@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Rod Taylor <rbt(at)rbt(dot)ca> writes:
> I'd like ALTER SEQUENCE to be transaction safe.
I think that's inherently impossible without breaking the existing
behavior of setval/nextval, which is something we will not accept.
ALTER SEQUENCE would be better thought of as a form of setval with
even more parameters, but not fundamentally different semantics.
> Can I assume that
> a standard simple_heap_update() is valid against the sequence,
You can be certain that it is not. There can be only one tuple in a
sequence table.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-12-09 21:22:20 | Re: psql's \d commands --- end of the line for 1-character identifiers? |
| Previous Message | Hannu Krosing | 2002-12-09 21:13:11 | Re: Sequence Cleanup |