Re: [HACKERS] fresh regression - regproc result contains unwanted schema - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] fresh regression - regproc result contains unwanted schema
Date
Msg-id 13691.1507994805@sss.pgh.pa.us
Whole thread Raw
In response to [HACKERS] fresh regression - regproc result contains unwanted schema  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: [HACKERS] fresh regression - regproc result contains unwanted schema
List pgsql-hackers
Pavel Stehule <pavel.stehule@gmail.com> writes:
> When function is overwritten, then regproc result contains schema, although
> it is on search_path

There's no "fresh regression" here, it's done that more or less since
we invented schemas.  See regprocout:
            * Would this proc be found (uniquely!) by regprocin? If not,            * qualify it.

git blame dates that comment to commit 52200bef of 2002-04-25.

Admittedly, qualifying the name might not be sufficient to disambiguate,
but regprocout doesn't have any other tool in its toolbox, so it uses
the hammer it's got.  If you're overloading functions, you really need
to use regprocedure not regproc.
        regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: [HACKERS] fresh regression - regproc result contains unwanted schema
Next
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] fresh regression - regproc result contains unwanted schema