On 18 October 2012 16:08, Robert Haas <robertmhaas@gmail.com> wrote:
> To make
> it even better, add some generic options that can be passed through to
> the underlying handler.
Agreed
>> 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.
>
> This might be better, but it's also possibly more mechanism than we
> truly need here. But then again, if we're going to end up with more
> than a handful of handlers, we probably do want to do this.
Let me have a play and see what comes out simplest. Somewhere in the
middle seems about right.
-- Simon Riggs http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
