Re: GROUP BY in CTE causes ELSE in outer query to be prematurely evaluated - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: GROUP BY in CTE causes ELSE in outer query to be prematurely evaluated
Date
Msg-id CAKFQuwZT0UaOiV+2h6f42_U_tU34wXH3Gv8BrjF_U168SWS5PQ@mail.gmail.com
Whole thread
In response to Re: GROUP BY in CTE causes ELSE in outer query to be prematurely evaluated  (Björn Kautler <Bjoern@kautler.net>)
Responses Re: GROUP BY in CTE causes ELSE in outer query to be prematurely evaluated
List pgsql-bugs
On Wednesday, March 4, 2026, Björn Kautler <Bjoern@kautler.net> wrote:

What I tried to do was to provoke the division-by-zero error if I happened to forget some WHEN branch as this is a bug.
Is there some safe way to do something like this you are aware of

Write a volatile “fail()” plpgsql function, and call it in the else block. Raise exception there.

 David J.

pgsql-bugs by date:

Previous
From: Björn Kautler
Date:
Subject: Re: GROUP BY in CTE causes ELSE in outer query to be prematurely evaluated
Next
From: Tom Lane
Date:
Subject: Re: GROUP BY in CTE causes ELSE in outer query to be prematurely evaluated