| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PSQL commands: \quit_if, \quit_unless |
| Date: | 2016-12-06 15:49:37 |
| Message-ID: | alpine.DEB.2.20.1612061616250.16863@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> But if it does make sense to share, then that's another reason for not
> designing something ad-hoc for psql: integrating it later will be more
> work in total.
Yes, but not much: evaluating "[!] :var" special syntax would be dropped,
but I do not think that it is the main issue with these features.
I understand that your conclusion is to require psql expressions +
conditions as one (large) patch.
Given my personnal experience with the patch process, my conclusion is
that I will very probably not do it. Just adding logical expressions to
pgbench, a minor feature for a minor client, has already been spread over
3 CF, and this is a part of what is required for the condition &
expression in psql.
Hopefully someone else will do it, and I'll do some reviewing then.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-12-06 15:52:47 | Re: tzdata 2016j |
| Previous Message | Vladimir Borodin | 2016-12-06 15:38:11 | tzdata 2016j |