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

From Pavel Stehule
Subject Re: [HACKERS] fresh regression - regproc result contains unwanted schema
Date
Msg-id CAFj8pRDE9MS3PnxpjcpK9npmweNgO6aRYOUBymVsBFrNVnGZAQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] fresh regression - regproc result contains unwanted schema  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers


2017-10-14 17:26 GMT+02:00 Tom Lane <tgl@sss.pgh.pa.us>:
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.

It is false alarm. I am sorry. I shot by self. Thank you for explanation

Nice evening.

Pavel


                        regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] fresh regression - regproc result contains unwanted schema
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] pg_control_recovery() return value when not in recovery