| From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Fix assorted inconsistencies in GIN opclass support function dec |
| Date: | 2016-05-02 20:38:48 |
| Message-ID: | CAPpHfdsp5zNTt_pfHN6DWrE3=DcBikMZrwHbbbyLLcbxgK6emw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, Jan 20, 2016 at 6:32 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> contrib/hstore/hstore--1.3.sql | 12 ++++-----
> contrib/intarray/intarray--1.1.sql | 8 +++---
> contrib/tsearch2/tsearch2--1.0.sql | 4 +--
>
Hmm... Is it correct to change function signatures without extension
version bump? pg_upgraded clusters would remain with old version of these
functions. Once we have instances with same extension version but with
different signatures of its functions, there is no correct way to refer
these functions in future. I think we should do the version bump in this
case.
The same for 9ff60273e35cad6e9d3a4adf59d5c2455afe9d9e.
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-05-02 21:09:48 | Re: pgsql: Fix assorted inconsistencies in GIN opclass support function dec |
| Previous Message | Alvaro Herrera | 2016-05-02 19:57:53 | pgsql: Fix thinko in comment |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2016-05-02 20:50:36 | Re: snapshot too old, configured by time |
| Previous Message | Andres Freund | 2016-05-02 20:36:34 | Re: [BUGS] Breakage with VACUUM ANALYSE + partitions |