| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [patch] Proposal for \crosstabview in psql |
| Date: | 2016-02-11 08:43:35 |
| Message-ID: | 20160211084335.mvpmzqdmn75h64x2@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-02-09 09:27:04 +0000, Dean Rasheed wrote:
> Looking at this patch, I have mixed feelings about it. On the one hand
> I really like the look of the output, and I can see that the non-fixed
> nature of the output columns makes this hard to achieve server-side.
> But on the other hand, this seems to be going way beyond the normal
> level of result formatting that something like \x does, and I find the
> syntax for sorting particularly ugly.
I've pretty similar doubts. Addinging features to psql which are complex
enough that it's likely that people will be forced to parse psql
output... On the other hand, a proper server side solution won't be
easy; so maybe this is a okay enough stopgap.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-02-11 08:46:23 | Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby |
| Previous Message | Andres Freund | 2016-02-11 08:20:17 | Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby |