| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Tim Clarke <tim(dot)clarke(at)minerva(dot)info>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: CROSSTAB( .. only one column has values... ) |
| Date: | 2021-01-05 19:12:58 |
| Message-ID: | CAFj8pRBzHJG5==nZGxS6RMSMR_zYNCAJawWtSKq11aRE+f8qCQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi
út 5. 1. 2021 v 19:45 odesílatel Joe Conway <mail(at)joeconway(dot)com> napsal:
> On 1/5/21 12:11 PM, Tim Clarke wrote:
> > imho the crosstab() function isn't a good implementation. The biggest
> failure it
> > has is that you must know exactly how many output columns you will have
> in the
> > result /_prior to running it
>
>
> *That* is a function of how Postgres set returning functions work, and not
> specific to crosstab(). It is not easily fixed. Patches to fix that would
> be
> welcomed!
>
Regards
Pavel
>
> Joe
>
> --
> Crunchy Data - http://crunchydata.com
> PostgreSQL Support for Secure Enterprises
> Consulting, Training, & Open Source Development
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2021-01-05 19:38:13 | Re: Max# of tablespaces |
| Previous Message | Joe Conway | 2021-01-05 18:53:56 | Re: CROSSTAB( .. only one column has values... ) |