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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
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-12 03:09:27
Message-ID: 20190212030927.GF1475@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Mon, Feb 11, 2019 at 03:36:17PM +1300, David Rowley wrote:
> Okay. Here's a modified patch with the enum.

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.
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Nitesh Yadav 2019-02-12 03:10:52 Data loss when reading the data from logical replication slot
Previous Message Michael Paquier 2019-02-12 03:04:25 Re: Re: BUG #15629: Typo in Documentation

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-02-12 03:18:25 Re: monitoring CREATE INDEX [CONCURRENTLY]
Previous Message Michael Paquier 2019-02-12 03:04:25 Re: Re: BUG #15629: Typo in Documentation