pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Darryl Snover <dsnover@electrainfo.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-bugs@lists.postgresql.org <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 18:30:12 +0000
Message-ID: <5B072ABD-0923-4CAC-8F22-199651355EDB@electrainfo.com> (raw)
In-Reply-To: <20200128181428.GA19971@alvherre.pgsql>
References: <20200128181428.GA19971@alvherre.pgsql>

> On Jan 28, 2020, at 1:14 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> 
> 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?
> 

No tables are partitioned.  Any attempts to create any referential integrity constraint on any tables causes the same crash.

I’m trying to prune down the database to rid it of any proprietary data, and see if I can get a reproducible small set.

-Darryl

view thread (4+ messages)

Message-ID: <5B072ABD-0923-4CAC-8F22-199651355EDB@electrainfo.com>
Permalink:  ../5B072ABD-0923-4CAC-8F22-199651355EDB@electrainfo.com/
Also on:    postgresql.org/message-id/5B072ABD-0923-4CAC-8F22-199651355EDB@electrainfo.com

 · 

reply

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: dsnover@electrainfo.com, alvherre@2ndquadrant.com
  Subject: Re: BUG #16237: When restoring database, backend disconnects or crashes when foreign key is created
  In-Reply-To: <5B072ABD-0923-4CAC-8F22-199651355EDB@electrainfo.com>
  References: <20200128181428.GA19971@alvherre.pgsql> <5B072ABD-0923-4CAC-8F22-199651355EDB@electrainfo.com>

* 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