| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Global Sequences |
| Date: | 2012-10-18 06:59:32 |
| Message-ID: | CA+U5nMLLr=U-SDSzOuG+JF8Z3LGRpJY97nt6oMsyH9uhptgBCQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16 October 2012 18:29, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2012-10-18 07:19:45 | Re: [RFC] CREATE QUEUE (log-only table) for londiste/pgQ ccompatibility |
| Previous Message | Simon Riggs | 2012-10-18 06:58:35 | Re: Global Sequences |