| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| 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 |
| Date: | 2020-07-07 15:08:30 |
| Message-ID: | 20200707150830.GA8895@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-Jul-07, Michael Paquier wrote:
> 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 ;)
That's a holdover from old times, when we thought functions were
procedures. That's no longer the case.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-07-07 15:09:49 | Re: Proposal: Automatic partition creation |
| Previous Message | Alvaro Herrera | 2020-07-07 15:06:39 | Re: pg_resetwal --next-transaction-id may cause database failed to restart. |