Re: PSQL commands: \quit_if, \quit_unless - Mailing list pgsql-hackers

From Robert Haas
Subject Re: PSQL commands: \quit_if, \quit_unless
Date
Msg-id CA+TgmoYRZWoS9j=+9CsX9+Uf42mFHE1WFQdJ3dFoaq-csYX6Vg@mail.gmail.com
Whole thread Raw
In response to Re: PSQL commands: \quit_if, \quit_unless  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: PSQL commands: \quit_if, \quit_unless  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Nov 29, 2016 at 4:43 AM, Pavel Stehule <pavel.stehule@gmail.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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Broken SSL tests in master
Next
From: Thomas Munro
Date:
Subject: Re: Logical Replication WIP