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

From Peter Eisentraut
Subject Re: proposal: plpgsql pragma statement
Date
Msg-id 5868982a-3bd8-776c-c443-ddcac1183436@2ndquadrant.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
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.

-- 
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 unique statement id
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: plpgsql pragma statement