| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: plpgsql pragma statement |
| Date: | 2018-12-06 17:16:55 |
| Message-ID: | CA+Tgmoafhygh1+e3EVmfGRR1SZ8220H4A2Amq4Th=7tJC1HmLg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 6, 2018 at 12:13 PM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> My idea about plpgsql PRAGMA is very close to PL/SQL or Ada PRAGMA. This is not runtime statement - the information from this command will be assigned to related object - function, block, command at parser time.
That's sensible, but the syntax you were proposing didn't look like it
was related to a specific statement. I was objecting to the idea that
PRAGMA whatever; should be construed as an annotation of,
specifically, the following statement.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2018-12-06 17:23:28 | Re: WIP: Avoid creation of the free space map for small tables |
| Previous Message | Pavel Stehule | 2018-12-06 17:12:44 | Re: proposal: plpgsql pragma statement |