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

From Pavel Stehule
Subject Re: proposal: plpgsql pragma statement
Date
Msg-id CAFj8pRBu+NeKRaM9M4kLkfx4yRDX0UmUdW0dL0pseV8vP_6xgA@mail.gmail.com
Whole thread Raw
In response to Re: proposal: plpgsql pragma statement  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: proposal: plpgsql pragma statement  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers


pá 4. 1. 2019 v 14:07 odesílatel Peter Eisentraut <peter.eisentraut@2ndquadrant.com> napsal:
On 06/12/2018 18:27, Pavel Stehule wrote:
> For my purpose I can imagine PRAGMA on function level with same syntax
> like PL/SQL - I need to push somewhere some information that I can use
> for plpgsql_check to protect users against false alarms. The locality in
> this moment is not too important for me. But I prefer solution that
> doesn't looks too strange, and is possible just with change plpgsql parser.

When you are about to warn about a particular statement, you have the
statement's line number, so you can look up the source code and check
for any disable-this-warning comments.

It means to write own lexer and preparse source code before I start checking.

I think so block level PRAGMA is significantly better solution



--
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: proposal: plpgsql pragma statement
Next
From: Andrey Borodin
Date:
Subject: Re: GiST VACUUM