From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] btree_gin, add support for uuid, bool, name, bpchar and anyrange types |
Date: | 2018-04-04 23:43:44 |
Message-ID: | f637cba1-1d7e-17ed-b39b-d01b02aa00e2@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 03/30/2018 10:51 PM, Matheus de Oliveira wrote:
> Hi all.
>
> On Wed, Mar 21, 2018 at 1:47 PM, Tomas Vondra
> <tomas(dot)vondra(at)2ndquadrant(dot)com <mailto:tomas(dot)vondra(at)2ndquadrant(dot)com>> wrote:
>
>
> Do you plan to post an updated version of the patch, of what is your
> response to the points raised last week?
>
>
> Very sorry about the long delay. I've been in a long trip, no time to
> look that carefully.
>
>
> I still haven't made my mind regarding usefulness of range opclasses, so
> I suggest to split the patch into two parts - 0001 for the opclasses
> we're confident are useful, and 0002 for those extras. The committer
> then may apply either 0001 or 0001+0002, depending on his judgment.
>
>
> I liked the idea. So, follows the patches:
> - 0001-btree_gin-uuid--base.v2.patch - all types but anyrange, and with
> the adjustments on comments you proposed
> - 0002-btree_gin-uuid--anyrange.v2.patch - adding the anyrange type
> (must be applied after 0001)
>
> Anything else missing?
>
I don't think so. I've marked it as RFC, but I have no idea if anyone is
going to push it by the end of this commitfest.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David Steele | 2018-04-05 00:03:54 | Re: PATCH: Configurable file mode mask |
Previous Message | Tatsuo Ishii | 2018-04-04 22:53:42 | Re: [HACKERS] [PATCH] Lockable views |