| From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>, Artur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Oleg Bartunov <obartunov(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, David Steele <david(at)pgmasters(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] [PATCH] Generic type subscripting |
| Date: | 2018-12-27 10:31:21 |
| Message-ID: | CA+q6zcXD=Tkx_=RtK4ePh04JP9vA356-VRM7KvDtBpMH39pQ+Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Mon, Nov 26, 2018 at 1:37 PM Dmitry Dolgov <9erthalion6(at)gmail(dot)com> wrote:
>
> Thanks for noticing! I was in rush when did rebase, and made few mistakes (the
> moral of the story - do not rush). Here is the fix, which is more aligned with
> the commit ab69ea9fee.
And one more rebase with pretty much the same functionality so far.
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Renaming-for-new-subscripting-mechanism-v17.patch | application/octet-stream | 54.9 KB |
| 0005-Subscripting-documentation-v17.patch | application/octet-stream | 20.0 KB |
| 0003-Subscripting-for-array-v17.patch | application/octet-stream | 13.8 KB |
| 0004-Subscripting-for-jsonb-v17.patch | application/octet-stream | 33.6 KB |
| 0002-Base-implementation-of-subscripting-mechanism-v17.patch | application/octet-stream | 62.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2018-12-27 10:39:36 | Re: Offline enabling/disabling of data checksums |
| Previous Message | Peter Eisentraut | 2018-12-27 10:04:09 | Re: [HACKERS] REINDEX CONCURRENTLY 2.0 |