Re: [PATCH] GROUP BY ALL
David G. Johnston <david.g.johnston@gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: David Christensen <david@pgguru.net>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-07-23T16:59:29Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add GROUP BY ALL.
- ef38a4d9756d 19 (unreleased) landed
-
Refactor to avoid code duplication in transformPLAssignStmt.
- b0fb2c6aa5a4 19 (unreleased) landed
-
Fix missed copying of groupDistinct in transformPLAssignStmt.
- b7f6798c056a 16.11 landed
- 9ca79896aba3 15.15 landed
- 78a284b0b8d4 18.1 landed
- 7504d2be9eb4 19 (unreleased) landed
- 3fc9aa5b0233 17.7 landed
- 0be39b4b1a01 14.20 landed
On Tue, Jul 23, 2024 at 9:48 AM David Christensen <david@pgguru.net> wrote: > > Sure, not everything that makes things easier is strictly necessary; > we could require `CAST(field AS text)` instead of `::text`, Probably should have...being standard and all. Though syntactic sugar is quite different from new behavior - transforming :: to CAST is straight-forward. make > subqueries required for transforming oids into specific system tables > instead of `::regfoo` casts, Since OID is non-standard this falls within our purview. any number of other choices, remove > `SELECT *` as a parse option, Again, standard dictated. but making it easier to do common things > interactively as a DBA has value as well. > > Agreed, but this isn't a clear-cut win, and doesn't have standard conformance to tip the scale over fully. Also, there are so many better tools for data exploration. Removing this quirk only marginally closes that gap. David J.