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

From Pavel Stehule
Subject Re: BUG #15572: Misleading message reported by "Drop function operation"on DB with functions having same name
Date
Msg-id 155300941700.16480.7948036003189357692.pgcf@coridan.postgresql.org
Whole thread Raw
Responses Re: BUG #15572: Misleading message reported by "Drop functionoperation" on DB with functions having same name
List pgsql-hackers
The following review has been posted through the commitfest application:
make installcheck-world:  tested, passed
Implements feature:       tested, passed
Spec compliant:           not tested
Documentation:            not tested

I read a discussion and I think so currently implemented behave (by last patch) is correct in all details.

I propose maybe more strongly comment fact so noError is applied only on "not found" event. In other cases, this flag
isignored and error is raised immediately there. I think so it is not good enough commented why.
 
This is significant change - in previous releases, noError was used like really noError, so should be commented more.

Regress tests are enough.
The patch is possible to apply without problems and compile without warnings

The new status of this patch is: Ready for Committer

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Online verification of checksums
Next
From: Andres Freund
Date:
Subject: Re: Offline enabling/disabling of data checksums