From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | David Micallef <david(dot)j(dot)micallef(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: group by true now errors with non-integer constant in GROUP BY |
Date: | 2023-09-18 00:22:55 |
Message-ID: | CAApHDvqRo8ZwkmkGoeUQU766DyObYW2jPcpUVqpYbu5sN9CTew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, 18 Sept 2023 at 12:00, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> > 2. In master only, remove the special case added in #1 and allow any
> > non-integer constants to be treated as expressions.
>
> > I think #2 is a good move for the following reasons:
>
> FTR, I still think this is a bad idea. It will add more confusion
> than it removes, and I don't buy that it will confer any advantages,
> because nobody asked for it previously.
I'm not dead set on it. I just don't think we can do exactly nothing
about this. At the very least we need to mention in REL_15_STABLE's
release-15.sgml in the incompatibilities section.
Another reason for #2 which I forgot to add was that it gets rid of
the need to have the "non-integer constant in ..." error message and
saves about 8 lines of code and a string constant table entry.
I'll happily wait to see if anyone else has any thoughts on this. The
votes seem roughly 2 vs 2 at the moment.
David
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Guo | 2023-09-18 02:23:39 | Re: BUG #18077: PostgreSQL server subprocess crashed by a SELECT statement with WITH clause |
Previous Message | Tom Lane | 2023-09-18 00:00:55 | Re: group by true now errors with non-integer constant in GROUP BY |