Re: group by true now errors with non-integer constant in GROUP BY - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: group by true now errors with non-integer constant in GROUP BY
Date
Msg-id CAH2-WzkZLdgYd8gVR-Qw4Mwu6spe1FUwyMxOwPGoW+j3RT90oA@mail.gmail.com
Whole thread Raw
In response to Re: group by true now errors with non-integer constant in GROUP BY  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: group by true now errors with non-integer constant in GROUP BY
List pgsql-bugs
On Sun, Sep 17, 2023 at 5:01 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> David Rowley <dgrowleyml@gmail.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 agree. Maintaining bug compatibility doesn't seem worth it in this instance.

David Micallef mentioned that only one query was affected. You have to
draw the line somewhere.

--
Peter Geoghegan



pgsql-bugs by date:

Previous
From: "daidewei@highgo.com"
Date:
Subject: Re: Re: a plpgsql bug
Next
From: PG Bug reporting form
Date:
Subject: BUG #18123: The execution plan for the left join is incorrect, returning incorrect rows of data.