From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Ash M <makmarath(at)hotmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #15572: Misleading message reported by "Drop function operation" on DB with functions having same name |
Date: | 2019-02-17 22:17:52 |
Message-ID: | CAKJS1f9=CdJotJBvjoQfNipPjaVXdDLN1+K-07QFehTGOYH+_g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Tue, 12 Feb 2019 at 16:09, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> FWIW, it makes me a bit uneasy to change this function signature in
> back-branches if that's the intention as I suspect that it gets used
> in extensions.. For HEAD that's fine of course.
I wondered about this too and questioned Tom about it above. There
was no response.
I just assumed Tom didn't think it was worth fiddling with in back-branches.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-02-17 22:31:43 | Re: BUG #15572: Misleading message reported by "Drop function operation" on DB with functions having same name |
Previous Message | David Rowley | 2019-02-17 22:15:19 | Re: BUG #15572: Misleading message reported by "Drop function operation" on DB with functions having same name |
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2019-02-17 22:21:29 | Re: dsa_allocate() faliure |
Previous Message | David Rowley | 2019-02-17 22:15:19 | Re: BUG #15572: Misleading message reported by "Drop function operation" on DB with functions having same name |