| From: | Emre Hasegeli <emre(at)hasegeli(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GiST support for inet datatypes |
| Date: | 2014-02-17 20:41:44 |
| Message-ID: | CAE2gYzxWUx_R1BExfHOBBkZxNVMRpnqLMNBq07Gb34EH7t=yKg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2014-02-17 22:16, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> More generally, it doesn't look to me like these upgrade scripts are
> complete; shouldn't they be creating some new objects, not just replacing
> old ones?
The actual patches are on the previous mail [1]. I was just trying
to solve the problem that btree_gist cannot be loaded because of
the new operator class.
> In short we probably need to think a bit harder about what this patch is
> proposing to do. It seems fairly likely to me that some other approach
> would be a better idea.
How about only removing the inet and the cidr operator classes
from btree_gist. btree-gist-drop-inet-v2.patch does that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-02-17 20:56:00 | Re: GiST support for inet datatypes |
| Previous Message | Andres Freund | 2014-02-17 20:36:51 | Re: Memory ordering issue in LWLockRelease, WakeupWaiters, WALInsertSlotRelease |