From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: condition blocks in psql |
Date: | 2015-06-28 12:21:52 |
Message-ID: | CAFj8pRCY-E87+=V52sYbpCfZmfbXD-CLZLhrb13K29B+k_U3Ew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2015-06-28 14:12 GMT+02:00 Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>:
> Hi,
>
> On 06/28/2015 09:04 AM, Fabien COELHO wrote:
>
>>
>> 2. The general difficulty of getting psql var values into a DO
>>> block (currently I use temp tables).
>>>
>>
>> Maybe this means that DO should be extended in some way to allow for
>> parameters, at least when PL/pgSQL is used?
>>
>
> I agree with this wholeheartedly. ISTM most of this thread is about
> limitations of our current DO implementation, partially addressed by adding
> a bunch of scripting commands, specific to psql. I don't think that's the
> right solution.
>
This proposal is not against to DO parametrization. It is same like
conditional block in C (#ifdef). There is similarity with C statements -
and both has sense.
Pavel
>
> regards
>
> --
> Tomas Vondra http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2015-06-28 12:26:57 | Re: proposal: condition blocks in psql |
Previous Message | Tomas Vondra | 2015-06-28 12:12:11 | Re: proposal: condition blocks in psql |