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

From Robert Haas
Subject Re: proposal: plpgsql pragma statement
Date
Msg-id CA+TgmoYkR=NvixYwU32c2zWUjgXSu4vNXCafpLqG=ydLC4kC8Q@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
List pgsql-hackers
On Thu, Dec 6, 2018 at 12:28 PM Pavel Stehule <pavel.stehule@gmail.com> wrote:
> please, can you propose, some what you like?
>
> For my purpose I can imagine PRAGMA on function level with same syntax like PL/SQL - I need to push somewhere some
informationthat I can use for plpgsql_check to protect users against false alarms. The locality in this moment is not
tooimportant for me. But I prefer solution that doesn't looks too strange, and is possible just with change plpgsql
parser.

Well, I haven't really studied this, but I would assume a
statement-level pragma would look like an annotation of some kind on
that particular statement, e.g.

PRAGMA plpgsql_check (magic pavel stuff goes here) SELECT ...

Rather than a separate statement:

PRAGMA plpgsql_check (magic pavel stuff goes here);
SELECT ...

This might be the wrong idea, I'm not an expert on this or anything.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: slow queries over information schema.tables
Next
From: Robert Haas
Date:
Subject: Re: rewrite ExecPartitionCheckEmitError