Re: fresh regression - regproc result contains unwanted schema

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: fresh regression - regproc result contains unwanted schema
Date: 2017-10-14 15:26:45
Message-ID: 13691.1507994805@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Pavel Stehule <pavel(dot)stehule(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2017-10-14 16:27:50 Re: fresh regression - regproc result contains unwanted schema
Previous Message Pavel Stehule 2017-10-14 13:14:27 fresh regression - regproc result contains unwanted schema