Re: BUG #16237: When restoring database, backend disconnects or crashes when foreign key is created

> On Jan 28, 2020, at 1:14 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)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