Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines
pinker <pinker@onet.eu>
From: pinker <pinker@onet.eu>
To: pgsql-bugs@postgresql.org
Date: 2020-10-18T21:25:44Z
Lists: pgsql-bugs
ala=# SELECT * FROM public.vacuum_dead_size(now()); server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: Failed. !?> \q [postgres@localhost ~]$ psql ala psql (13.0) Type "help" for help. ala=# update table_sizes set table_name = 'promotionuuu'; UPDATE 2 ala=# SELECT * FROM public.vacuum_dead_size(now()); schemaname | relname | total_bytes | dead_tup_size ------------+---------+-------------+--------------- (0 rows) ala=# SELECT * FROM public.vacuum_dead_size(now()); schemaname | relname | total_bytes | dead_tup_size ------------+---------+-------------+--------------- (0 rows) ala=# update table_sizes set table_name = 'promotion'; UPDATE 2 ala=# SELECT * FROM public.vacuum_dead_size(now()); server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: Failed. !?> \q -- Sent from: https://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html
Commits
-
Fix list-munging bug that broke SQL function result coercions.
- 25378db74fd9 13.1 landed
- c8ab9701791e 14.0 landed