From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
cc: Marko Tiikkaja <marko@joh.to>, Daniel Verite <daniel@manitou-mail.org>,
 PostgreSQL hackers <pgsql-hackers@postgresql.org>
Subject: Re: psql: add \pset true/false
In-reply-to: <5644FCE0.2030405@gmx.net>
References: <0949c317-3ec4-4516-a3aa-33a6cfbf5267@mm>
 <5631FCAF.9060204@joh.to> <27336.1446126627@sss.pgh.pa.us>
 <5644FCE0.2030405@gmx.net>
Comments: In-reply-to Peter Eisentraut <peter_e@gmx.net>
 message dated "Thu, 12 Nov 2015 15:56:00 -0500"
Date: Thu, 12 Nov 2015 16:09:40 -0500
Message-ID: <20643.1447362580@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Peter Eisentraut <peter_e@gmx.net> writes:
> Plus we already have \pset numericlocale as a similar feature in psql.

But \pset numericlocale is also a crock.  It doesn't affect COPY output
for instance, and its ability to identify which data types it should apply
to is really shaky.  And it's virtually unused, as demonstrated by the
fact that serious bugs in it went undetected for many years (cf 4778a0bda,
77130fc14).  That's a really poor advertisement for the usefulness of the
proposed feature.

			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