Rod Taylor kirjutas T, 10.12.2002 kell 01:49:
> Below is a short list of TODOs on sequences I wish to tackle over the
> next week.
...
> Ok, this is where it gets confusing.  Right now setval() is implemented
> in such a manner that it cannot be rolled back (see SETVAL NOTE below),
> but I'd like ALTER SEQUENCE to be transaction safe.

All *val('seqname') functions are transaction-unsafe, i.e. live outside
transactions. 

Why would you want alter transaction to be transaction safe ? 


-- 
Hannu Krosing <[EMAIL PROTECTED]>

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to