| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Petr Jelinek <petr(at)2ndquadrant(dot)com> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Vik Fearing <vik(at)2ndquadrant(dot)fr>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Sequence Access Method WIP |
| Date: | 2016-01-18 08:17:37 |
| Message-ID: | CAMsr+YETwmoL2tGa8Zvsq8D8VM=oMPM1zYPMYZge-3tzpCG29A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1 January 2016 at 07:51, Petr Jelinek <petr(at)2ndquadrant(dot)com> wrote:
>
> Other than that, this is based on the new am api by Alexander Korotkov
> [1]. It extends it by adding another column called amkind to the pg_am
> which can have either value "i" for index or "S" for sequence (same as
> relkind in pg_class for those).
>
This patch will no longer apply after 65c5fcd353 (
http://github.com/postgres/postgres/commit/65c5fcd353) as outlined in
http://www.postgresql.org/message-id/10804.1453077804@sss.pgh.pa.us .
Setting waiting-on-author in the CF app.
The good news is that the commit of the pg_am rework greatly eases the path
of this patch into core.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2016-01-18 08:19:20 | Re: Sequence Access Method WIP |
| Previous Message | Craig Ringer | 2016-01-18 08:10:16 | Re: Do we need SQL-level access to amoptions functions? |