From: | Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru> |
---|---|
To: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Steele <david(at)pgmasters(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Generic type subscripting |
Date: | 2017-09-09 21:33:49 |
Message-ID: | 20170909213349.GA17898@arthur.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Sep 07, 2017 at 10:49:54PM +0200, Dmitry Dolgov wrote:
> On 29 August 2017 at 22:42, Dmitry Dolgov <9erthalion6(at)gmail(dot)com> wrote:
> >
> > To make a review little bit easier I've divided the patch into a few
> smaller parts.
>
> Apparently I forgot about subscripting for the name data type, so here is a
> small update of the patch.
Thank you for rebasing the patch!
PostgreSQL and documentation with the patch compiles without any errors. All regression tests passed.
But honestly I still cannot say that I agree with *_extract() and *_assign() functions creation way. For example, there is no entry in pg_depend for them (related with pg_type entry).
Because there is no such entry, there is the following bug:
1 - make and install src/tutorial
2 - run src/tutorial/subscripting.sql
3 - run:
=# drop function custom_subscripting_extract(internal);
4 - and we get the error:
=# select data[0] from test_subscripting;
ERROR: function 0x55deb7911bfd returned NULL
But of course it is only my opinion and I could be wrong.
--
Arthur Zakirov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2017-09-09 22:23:54 | Re: segment size depending *_wal_size defaults (was increasing the default WAL segment size) |
Previous Message | Tom Lane | 2017-09-09 15:38:50 | Re: Still another race condition in recovery TAP tests |