Re: PATCH: pgbench allow '=' in \set

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PATCH: pgbench allow '=' in \set
Date: 2015-05-14 16:18:55
Message-ID: alpine.DEB.2.10.1505141812500.1821@sto
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> [...] I tend to agree with the bottom line that that's just more
> complication than is justified. I sympathize with Robert's dislike for
> backslash continuations; but doing it the other way would be a huge
> amount of up-front work and a nontrivial amount of continuing
> maintenance, for which we would not get thanks from users but rather
> bitching about how we broke their scripts. Seems like a lose-lose
> situation.

I agree. It is a small matter that does not justify a large patch, a
greater maintenance burden and breaking compatibility.

I've posted a small patch for backslash-continuations as a new thread.

--
Fabien.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-05-14 16:19:44 Re: upper planner path-ification
Previous Message Stephen Frost 2015-05-14 16:10:32 Re: pgsql: Add pg_audit, an auditing extension