| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | dsnover(at)electrainfo(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16237: When restoring database, backend disconnects or crashes when foreign key is created |
| Date: | 2020-01-28 18:14:28 |
| Message-ID: | 20200128181428.GA19971@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Darryl Snover | 2020-01-28 18:30:12 | Re: BUG #16237: When restoring database, backend disconnects or crashes when foreign key is created |
| Previous Message | Tom Lane | 2020-01-28 17:34:37 | Re: postgres crash on concurrent update of inheritance partitioned table |