MIME-Version: 1.0
References: <CAHM0NXjz0kDwtzoe-fnHAqPB1qA8_VJN0XAmCgUZ+iPnvP5LbA@mail.gmail.com>
 <CAKFQuwY0vhNG8T+pC3BQJurFi3NN_L1KbEPGagRN3V5nKZcpDQ@mail.gmail.com> <CAHM0NXgVfYYt1Yw6iVqGY9PZ=dVPe6HhEByH9uD-H-AA0z_1Zg@mail.gmail.com>
In-Reply-To: <CAHM0NXgVfYYt1Yw6iVqGY9PZ=dVPe6HhEByH9uD-H-AA0z_1Zg@mail.gmail.com>
From: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Date: Wed, 24 Jul 2024 19:42:01 +0530
Message-ID: <CAExHW5tn_Bk1iFOWtmr9VsbjueTDM13O98gH8MrqQ8KnOs2MmA@mail.gmail.com>
Subject: Re: [PATCH] GROUP BY ALL
To: David Christensen <david@pgguru.net>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>, 
	pgsql-hackers <pgsql-hackers@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAExHW5tn_Bk1iFOWtmr9VsbjueTDM13O98gH8MrqQ8KnOs2MmA%40mail.gmail.com>
Precedence: bulk

On Tue, Jul 23, 2024 at 6:53=E2=80=AFPM David Christensen <david@pgguru.net=
> wrote:
>
> On Mon, Jul 22, 2024 at 4:34=E2=80=AFPM David G. Johnston
> <david.g.johnston@gmail.com> wrote:
> >
> > On Mon, Jul 22, 2024 at 1:55=E2=80=AFPM David Christensen <david@pgguru=
.net> wrote:
> >>
> >> I see that there'd been some chatter but not a lot of discussion about
> >> a GROUP BY ALL feature/functionality.  There certainly is utility in
> >> such a construct IMHO.
> >>
> >> Still need some docs; just throwing this out there and getting some fe=
edback.
> >>
> >
> > I strongly dislike adding this feature.  I'd only consider supporting i=
t if it was part of the SQL standard.
> >
> > Code is written once and read many times.  This feature caters to the w=
riter, not the reader.  And furthermore usage of this is prone to be to the=
 writer's detriment as well.
>
> I'd say this feature (at least for me) caters to the investigator;
> someone who is interactively looking at data hence why it would cater
> to the writer.  Consider acquainting yourself with a large table that
> has a large number of annoying-named fields where you want to look at
> how different data is correlated or broken-down.  Something along the
> lines of:

To me this looks like a feature that a data exploration tool may
implement instead of being part of the server. It would then provide
more statistics about each correlation/column set etc.

--=20
Best Wishes,
Ashutosh Bapat