Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines

From: pinker <pinker(at)onet(dot)eu>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines
Date: 2020-10-18 21:25:44
Message-ID: 1603056344945-0.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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(at)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message pinker 2020-10-18 21:37:27 Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines
Previous Message pinker 2020-10-18 21:18:55 Re: Postgres 13 signal 11: Segmentation fault tested on 2 independent machines