Re: merging some features from plpgsql2 project

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Marko Tiikkaja <marko(at)joh(dot)to>
Subject: Re: merging some features from plpgsql2 project
Date: 2017-01-04 21:07:09
Message-ID: CAHyXU0y8kynx8gdi_WiASjAuwyCHu0LXchjfZjkSgxbwztS2LQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 4, 2017 at 1:49 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>
>>
>> so some possible design can be:
>>
>> DECLARE
>> PRAGMA UNCACHED_PLANS;
>> BEGIN
>> SELECT ... INTO ;
>> SELECT ... INTO ;
>> END;
>>
>> This respects Ada and PL/SQL style - probably easy implementation
>>
>> Regards
>>
>> Pavel
>
>
> some examples based on Ada doc
>
> FUNCTION xxx RETURN int AS
> PRAGMA yyy -- pragma has function scope
> BEGIN
>
> FUNCTION xxx RETURN int AS
> BEGIN
> DECLARE
> PRAGMA yyy -- pragma has block scope

ok, sub-block makes sense over statement level IMO.

merlin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-01-04 21:15:58 Re: pgbench - allow to store select results into variables
Previous Message Robert Haas 2017-01-04 20:50:12 Re: Declarative partitioning - another take