| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Daniel Verite <daniel(at)manitou-mail(dot)org>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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-03-13 23:05:16 |
| Message-ID: | 56E5F22C.90906@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/13/16 12:48 AM, Pavel Stehule wrote:
> crosstabview is really visualization tool. **But now, there are not any
> other tool available from terminal.** So this can be significant help to
> all people who would to use this functionality.
Not just the terminal either. Offhand I'm not aware of *any* fairly
simple tool that provides crosstab. There's a bunch of
complicated/expensive BI tools that do, but unless you've gone through
the trouble of getting one of those setup you're currently pretty stuck.
Ultimately I'd really like some way to remove/reduce the restriction of
result set definitions needing to be determined at plan time. That would
open the door for server-side crosstab/pivot as well a a host of other
things (such as dynamically turning a hstore/json/xml field into a
recordset).
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-03-13 23:30:04 | Re: checkpointer continuous flushing - V18 |
| Previous Message | Jim Nasby | 2016-03-13 22:54:30 | Re: amcheck (B-Tree integrity checking tool) |