Re: PostgreSQL error (Segmentation Fault with message "SSL SYSCALL error: EOF detected")

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: angell2006(at)ukr(dot)net
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: PostgreSQL error (Segmentation Fault with message "SSL SYSCALL error: EOF detected")
Date: 2018-11-09 14:25:23
Message-ID: 15219.1541773523@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

angell2006(at)ukr(dot)net writes:
> If I execute queries:

> DROP TABLE IF EXISTS client_tt;
> CREATE TABLE client_tt(id_client_tt integer NOT NULL, id_unique integer);
> INSERT INTO client_tt(id_client_tt, id_unique) VALUES('1', '1');
> ALTER TABLE ONLY client_tt ADD CONSTRAINT client_tt_pkey PRIMARY KEY (id_client_tt);
> ALTER TABLE ONLY client_tt ADD CONSTRAINT client_tt_ibfk_7 FOREIGN KEY (id_unique) REFERENCES client_tt(id_client_tt) ON DELETE SET NULL DEFERRABLE;
> ALTER TABLE client_tt ADD COLUMN tt_code_inn VARCHAR(12) NOT NULL DEFAULT '';
> DELETE FROM client_tt;

This looks like a known bug that's fixed in 11.1, released yesterday.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Magnus Hagander 2018-11-09 14:43:39 Re: BUG #15492: pg_cancel_backend(pg_backend_pid()) returns true sporadically
Previous Message Camila Gonçalves 2018-11-09 13:55:03 Re: Compatibility issues with version 9.5