Re: BUG #16237: When restoring database, backend disconnects orcrashes when foreign key is created - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #16237: When restoring database, backend disconnects orcrashes when foreign key is created
Date
Msg-id 20200128181428.GA19971@alvherre.pgsql
Whole thread Raw
In response to BUG #16237: When restoring database, backend disconnects or crashes when foreign key is created  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #16237: When restoring database, backend disconnects orcrashes when foreign key is created  (Darryl Snover <dsnover@electrainfo.com>)
List pgsql-bugs
On 2020-Jan-28, PG Bug reporting form wrote:

> pg_restore: creating FK CONSTRAINT
> "public.file_transit_transaction_file_transit_id_fkey"
> pg_restore: from TOC entry 3972; 2606 4177792 FK CONSTRAINT
> file_transit_transaction_file_transit_id_fkey postgres
> pg_restore: error: could not execute query: server closed the connection
> unexpectedly
>     This probably means the server terminated abnormally
>     before or while processing the request.
> Command was: ALTER TABLE ONLY file_transit_transaction
>     ADD CONSTRAINT file_transit_transaction_file_transit_id_fkey FOREIGN KEY
> (file_transit_id) REFERENCES file_transit(file_transit_id);

Is any of these tables (file_transit_transaction and file_transit)
partitioned?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: postgres crash on concurrent update of inheritance partitioned table
Next
From: Darryl Snover
Date:
Subject: Re: BUG #16237: When restoring database, backend disconnects orcrashes when foreign key is created