Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan
Date
Msg-id CAFj8pRBMWFbsJbbLwD0RjGePmjm4xTtUvAmLCZk9V=+_+2rW2w@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
Tree view



>
> SET x = .., y = .. SELECT ... ;

This seems pretty ugly from a syntax perspective.

We already have 'SET LOCAL', which manages scope to the current
transaction.  How about SET BLOCK which would set until you've left
the current statement block?

This is reason why PRAGMA was designed - it can works on function, block, or statement level. But only in block based PL languages.
 

merlin

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Still another race condition in recovery TAP tests
Next
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] Re: proposal - using names as primary names of plpgsqlfunction parameters instead $ based names