From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: GiST support for UUIDs |
Date: | 2015-06-25 16:50:25 |
Message-ID: | 5006.1435251025@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> writes:
> On Thu, Jun 25, 2015 at 8:06 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> writes:
>>> I'm interested in adding GiST support for the UUID column type
>>> . . . . So I'm curious where this change would go?
>> btree_gist, I'd think
> Okay, thank you for your answer! I was worried about the effects of
> having btree_gist depend on uuid-ossp. People won't have to say
> `CREATE EXTENSION "uuid-ossp"` if they only want `btree_gist`, right?
No, the uuid type exists in core. It's only some creation functions that
are in that extension.
>> the overhead of an extension version bump will probably
>> exceed the useful payload :-(
> Sorry to put more work on your plate. :-) I'm trying to pick something
> easy to get my feet wet.
That work will be on your plate actually ;-). Read the docs concerning
creation of new extension versions, and perhaps look in our git history
for previous commits that have upgraded contrib extensions.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2015-06-25 16:54:39 | Re: Serialization errors in Postgres 9.4.0 |
Previous Message | Jeff Janes | 2015-06-25 16:06:31 | Re: pgbench - allow backslash-continuations in custom scripts |