| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Petr Jelinek <petr(at)2ndquadrant(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Sequence Access Method WIP |
| Date: | 2014-11-07 23:45:39 |
| Message-ID: | 9D8BE011-5E2E-4608-A716-8B7FB90B745F@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Nov 5, 2014, at 5:43 PM, Petr Jelinek <petr(at)2ndquadrant(dot)com> wrote:
> I don't see how to make that work with ALTER SEQUENCE USING to be honest and I do care quite a lot about that use-case (I think the ability to convert the "local" sequences to 3rd party ones and back is very important).
What specific problems do you foresee? There's an issue if something depends on one of the added sequence columns, but if that is the case then you had *better* fail.
I think that the debugability value of making extra sequence columns human-readable is quite high.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2014-11-07 23:57:41 | Re: Sequence Access Method WIP |
| Previous Message | Robert Haas | 2014-11-07 23:36:55 | Re: tracking commit timestamps |