On Tue, Mar 9, 2021 at 7:27 AM Peter Eisentraut
<[email protected]> wrote:
>
>
> I see. The problem is that we don't have serialization and
> deserialization support for most utility statements. I think I'll need
> to add that eventually. For now, I have added code to prevent utility
> statements. I think it's still useful that way for now.
>
Great! thanks!
I found another problem when using CASE expressions:
CREATE OR REPLACE FUNCTION foo_case()
RETURNS boolean
LANGUAGE SQL
BEGIN ATOMIC
select case when random() > 0.5 then true else false end;
END;
apparently the END in the CASE expression is interpreted as the END of
the function
--
Jaime Casanova
Director de Servicios Profesionales
SYSTEMGUARDS - Consultores de PostgreSQL
