From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, Daniel Verite <daniel(at)manitou-mail(dot)org>, PostgreSQL hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql: add \pset true/false |
Date: | 2015-11-16 01:34:43 |
Message-ID: | 564932B3.90708@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/12/15 4:09 PM, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)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.
Just because people don't find much use for a feature doesn't mean it's
wrong in principle.
Clearly, people occasionally want to change how a data type displays in
psql. We could implement this in the server. But then we put a burden
on all non-psql clients to begin all their connections with a growing
number of RESET foo_display calls, and that's not very efficient. I
think it's up to each client to figure out how to display stuff and to
customize it if necessary.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2015-11-16 01:37:16 | Re: psql: add \pset true/false |
Previous Message | Peter Eisentraut | 2015-11-16 01:24:36 | Re: proposal: multiple psql option -c |