Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: BUG #15572: Misleading message reported by "Drop function operation" on DB with functions having same name
Date
Msg-id 19400.1546994166@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #15572: Misleading message reported by "Drop functionoperation" on DB with functions having same name  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: BUG #15572: Misleading message reported by "Drop functionoperation" on DB with functions having same name  (David Rowley <david.rowley@2ndquadrant.com>)
List pgsql-bugs
Tree view 
David Rowley <david.rowley@2ndquadrant.com> writes:
> Why can't we just remove the !noError check in the location where the
> error is raised?

I don't like that a bit --- the point of noError is to prevent throwing
errors, and it doesn't seem like it should be LookupFuncName's business
to decide it's smarter than its callers.  Maybe we need another flag
argument?

            regards, tom lane

pgsql-bugs by date:

Previous
From: CNG L
Date:
Subject: Is this a bug in auto vacuum worker?
Next
From: Thomas Munro
Date:
Subject: Re: BUG #15577: Query returns different results when executedmultiple times