| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, PostgreSQL <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PSQL commands: \quit_if, \quit_unless |
| Date: | 2016-12-02 01:52:29 |
| Message-ID: | CA+TgmoYRZWoS9j=+9CsX9+Uf42mFHE1WFQdJ3dFoaq-csYX6Vg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 29, 2016 at 4:43 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> I prefer the commands instead symbols - the parsing and processing symbols
> should be more complex than it is now. A psql parser is very simple - and
> any complex syntax enforces lot of code.
>
> \if_not
Given the precedent in pgbench (cf.
878fdcb843e087cc1cdeadc987d6ef55202ddd04), I think it requires an
amazing level of optimism to suppose we won't eventually end up with a
full-blown expression language here. I would suggest designing one
from the beginning and getting it over with. Even if you manage to
hold the line and exclude it from whatever gets committed initially,
somebody's going to propose it 2 years from now. And again 4 years
from now. And again 2 years after that.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2016-12-02 01:55:16 | Re: Logical Replication WIP |
| Previous Message | Michael Paquier | 2016-12-02 01:50:30 | Re: pgsql: Use latch instead of select() in walreceiver |