From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: dsnover@electrainfo.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16237: When restoring database, backend disconnects or crashes when foreign key is created
Date: Tue, 28 Jan 2020 15:14:28 -0300
Message-ID: <20200128181428.GA19971@alvherre.pgsql> (raw)
In-Reply-To: <16237-4b97757867332823@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: alvherre@2ndquadrant.com, dsnover@electrainfo.com
Subject: Re: BUG #16237: When restoring database, backend disconnects or crashes when foreign key is created
In-Reply-To: <20200128181428.GA19971@alvherre.pgsql>
References: <16237-4b97757867332823@postgresql.org> <20200128181428.GA19971@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox