Re: proposal: plpgsql pragma statement - Mailing list pgsql-hackers

From Jonah H. Harris
Subject Re: proposal: plpgsql pragma statement
Date
Msg-id CADUqk8WWXMn2Umdw2k3xk8vb+syXVeS5u0pfYGTBgCSwpTBn1g@mail.gmail.com
Whole thread Raw
In response to Re: proposal: plpgsql pragma statement  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: proposal: plpgsql pragma statement  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
You can alter the lexer and create a comment node, right? That’s how we did hints in EnterpriseDB.

On Wed, Dec 5, 2018 at 11:41 AM Pavel Stehule <pavel.stehule@gmail.com> wrote:


st 5. 12. 2018 v 15:03 odesílatel Pavel Luzanov <p.luzanov@postgrespro.ru> napsal:

But maybe your extension could read the PERFORM statement preceding it and treat it as an annotation hint for the following statement.

In this case, comment line in some format will be better than real PERFORM statement. Like this:


/*+PRAGMA cmdtype CREATE; */
EXECUTE format('CREATE TABLE xxx ...

I looked there and It is not possible to implement it - plpgsql uses SQL lexer, and the content of comments are just ignored. So I cannot to read comments. There is not any possibility to read it simply from plpgsql. Unfortunately, but it is expected, there is nothing like query string for plpgsql statement.

Regards

Pavel 
 
-----
Pavel Luzanov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

--
Jonah H. Harris

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal: plpgsql pragma statement
Next
From: Tom Lane
Date:
Subject: Re: slow queries over information schema.tables