From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | proposal: plpgsql pragma statement |
Date: | 2018-12-04 17:12:46 |
Message-ID: | CAFj8pRALJQnTbvc-Vt-5Lni8C8CtRS0S249hqN9=so+6bmhyqQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
I wrote plpgsql_check https://github.com/okbob/plpgsql_check.
It is working well, but because it does static analyse only, sometimes it
can produces false alarms or it should to stop a analyse, because there are
not necessary data.
https://github.com/okbob/plpgsql_check/issues/36
I see one possible solution in introduction of pragma statement with syntax:
PRAGMA keyword [content to semicolon];
The pragma has a relation to following statement. So the issue 36 can be
solved by pragma
PRAGMA cmdtype CREATE;
EXECUTE format('CREATE TABLE xxx ...
The PRAGMA statement does nothing in runtime. It works only in compile
time, and add a pair of key, value to next non pragma statement. This
information can be used by some plpgsql extensions.
What do you think about this proposal?
Regards
Pavel
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2018-12-04 18:41:59 | Re: psql display of foreign keys |
Previous Message | Andres Freund | 2018-12-04 17:01:04 | Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock |