From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: fresh regression - regproc result contains unwanted schema |
Date: | 2017-10-14 16:27:50 |
Message-ID: | CAFj8pRDE9MS3PnxpjcpK9npmweNgO6aRYOUBymVsBFrNVnGZAQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2017-10-14 17:26 GMT+02:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> 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.
>
It is false alarm. I am sorry. I shot by self. Thank you for explanation
Nice evening.
Pavel
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-10-14 17:45:22 | Re: pg_control_recovery() return value when not in recovery |
Previous Message | Tom Lane | 2017-10-14 15:26:45 | Re: fresh regression - regproc result contains unwanted schema |