From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fabien COELHO <coelho@cri.ensmp.fr>
cc: Corey Huinker <corey.huinker@gmail.com>,
        Daniel Verite <daniel@manitou-mail.org>,
        "David G. Johnston" <david.g.johnston@gmail.com>,
        Greg Stark <stark@mit.edu>, Erik Rijkers <er@xs4all.nl>,
        Robert Haas <robertmhaas@gmail.com>,
        Jim Nasby <Jim.Nasby@bluetreble.com>,
        PostgreSQL <pgsql-hackers@postgresql.org>
Subject: Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if,
 \quit_unless)
In-reply-to: <alpine.DEB.2.20.1703301812100.18789@lancre>
References: <df2c433c-b9ff-4d41-ad08-b0d420b403b8@manitou-mail.org>
 <alpine.DEB.2.20.1703250719430.8361@lancre>
 <CADkLM=esbih=DF97=87UjpT-8JjYnLCBy_NFMyM0vs-0jzYe3A@mail.gmail.com>
 <alpine.DEB.2.20.1703251857540.8361@lancre>
 <CADkLM=dZt6eJQD1pQ7GXUeP83Ut_N+RaRsCgDj+Cpx_bV=LLsg@mail.gmail.com>
 <alpine.DEB.2.20.1703270655240.20202@lancre>
 <CADkLM=fbEGfea0idN_XsKUG70JmCaMjdejo35q-B5tpC11NTuA@mail.gmail.com>
 <alpine.DEB.2.20.1703271631250.10424@lancre>
 <CADkLM=czttdEn1fVMb-qAQDvteXU3SOv47GsKbea9+iaYbCK_w@mail.gmail.com>
 <alpine.DEB.2.20.1703272110480.19631@lancre>
 <CADkLM=eUksHSUc_HXE8CRFgj85C8cABVfVY1hRoTfdNvwwOUGg@mail.gmail.com>
 <24980.1490748720@sss.pgh.pa.us> <21747.1490796899@sss.pgh.pa.us>
 <alpine.DEB.2.20.1703292000520.17210@lancre>
 <CADkLM=cbF9yLTeU6T_sMxrrpZhxQH_Y+bNXdOFiGn8oVXjBngg@mail.gmail.com>
 <alpine.DEB.2.20.1703292248410.20346@lancre> <10990.1490847359@sss.pgh.pa.us>
 <alpine.DEB.2.20.170330084! 3020.2076@lancre>
 <18081.1490888751@sss.pgh.pa.us> <alpine.DEB.2.20!
 .1703301812100.18789@lancre>
Comments: In-reply-to Fabien COELHO <coelho@cri.ensmp.fr>
	message dated "Thu, 30 Mar 2017 18:22:23 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <25878.1490892889.1@sss.pgh.pa.us>
Date: Thu, 30 Mar 2017 12:54:49 -0400
Message-ID: <25879.1490892889@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Fabien COELHO <coelho@cri.ensmp.fr> writes:
>> If it actually is impossible to give pgbench equivalent behavior, we'll 
>> just have to live with the discrepancy,

> Yep.

>> but ISTM it could probably be made to work.

> Even if it could somehow, I do not see it as a useful feature for pgbench. 

Perhaps not.

> I also lack a good use case for psql for this feature.

It doesn't seem very outlandish to me: the alternative would be to repeat
all of a query that might span dozens of lines, in order to change one or
two lines.  That's not very readable or maintainable.

I'm prepared to believe that extremely long queries aren't ever going
to be common in pgbench scripts, so that there's not much need to support
the equivalent behavior in pgbench.  So maybe it's fine.

			regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers