|From:||Michael Paquier <michael(at)paquier(dot)xyz>|
|To:||Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>|
|Cc:||Daniel Gustafsson <daniel(at)yesql(dot)se>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>|
|Subject:||Re: Cache lookup errors with functions manipulation object addresses|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Mon, Jul 06, 2020 at 10:56:53AM -0400, Alvaro Herrera wrote:
> I think "routine" was more correct. We introduced that terminology to
> encompass both functions and procedures, back when real procedures were
> added. See the definitions in the glossary for example.
Okay, fine by me, while we have getProcedureTypeDescription() working
on pg_proc entries ;)
> I'm not sure that I'll have time to review this in the next couple of
> days, but it seemed sufficiently good when I last looked.
Thanks. I'll try to come back to it next week or the one after for
another round of self-review, and I'll see what to do at this point.
This has been around for three years, it can still wait a bit.
|Next Message||vignesh C||2020-07-07 05:50:51||Re: Parallel copy|
|Previous Message||Michael Paquier||2020-07-07 05:35:48||Re: A patch for get origin from commit_ts.|