On 16 October 2012 18:29, Tom Lane <t...@sss.pgh.pa.us> wrote: > Or maybe better, invent a level of indirection like a "sequence access > method" (comparable to index access methods) that provides a compatible > set of substitute functions for sequence operations. If you want to > override nextval() for a sequence, don't you likely also need to > override setval(), currval(), etc? Not to mention overriding ALTER > SEQUENCE's behavior.
Agreed, though with exact API as discussed on portion of thread with Markus. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
