SYSTEM_TIME (start_timestamp, end_timestamp)
);
\d test
it failes after outputting the table informations with this backtrace:
free(): invalid pointer
[1]587783 abort (core dumped) psql -X -U easteregg -h localhost postgres
(gdb) bt 50
#0 __GI_raise (sig=sig@entry=6) at
> Probably the fix is not hard, but it is almost the same situation as the
> UNION case. The result of your code is not deterministic
>
> If there are more different ti_resource_id then some values can be randomly
> ignored - when hash agg is used.
>
> The safe fix should be
>
> _resource_id :=
the code provided is just a little poc to get the error ( which i have not
included with my first mail sorry. )
ERROR: syntax error at or near "DISTINCT"
LINE 8: _test := DISTINCT a FROM ( VALUES ( (true), ( true ) ) )...
the code in production looked like this:
_resource_id :=
hi,
no noticed after the assignment with union (
https://www.postgresql.org/message-id/flat/20210105201257.f0d76aff%40mail.verfriemelt.org
), that the assignment with distinct is broken aswell.
DO $$
DECLARE
_test bool;
BEGIN
_test := DISTINCT a FROM ( VALUES ( (true), ( true
to be clear, that was existing code within our codebase, it was used as a very
bad alternative to an if/else clause. think of it as an tenery operator. thats
just straight up bad code as tom said. but even if it is, its a change and i
wanted to check, if its intended. so thank you for you time a
hi,
i updated our ci pipeline to the latest 14-devel build from the postgresql apt
repository:
PostgreSQL 14devel (Debian 14~~devel~20210105.1140-1~285.gitbc43b7c.pgdg110+1)
on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-3) 10.2.1 20201224,
64-bit
i found, that the behaviour of var
