Re: BUG #15572: Misleading message reported by "Drop function operation" on DB with functions having same name

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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-10 22:05:54
Message-ID: CAKJS1f-6kdi2KyyCuHf4fM-Cuz4w99D1mMsOxhQEw2oaA5tW8g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-bugs pgsql-hackers

On Thu, 7 Feb 2019 at 01:17, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> wrote:
> Updated patch attached.

Updated patch attached again. This time due to a newly added call to
LookupFuncName() in 1fb57af92.

--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

Attachment Content-Type Size
drop_func_if_not_exists_fix_v4.patch application/octet-stream 18.7 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-02-10 22:39:19 Re: BUG #15572: Misleading message reported by "Drop function operation" on DB with functions having same name
Previous Message Sergey Ivanov 2019-02-10 21:20:32 Re: BUG #15627: libpq memory leak

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-02-10 22:39:19 Re: BUG #15572: Misleading message reported by "Drop function operation" on DB with functions having same name
Previous Message Tom Lane 2019-02-10 21:55:30 Re: Reporting script runtimes in pg_regress