| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | ana-mur21s(at)yandex(dot)ru |
| Subject: | BUG #15723: Export fails 'worker process died unexpectedly' but no error in pg_dump |
| Date: | 2019-03-29 08:54:38 |
| Message-ID: | 15723-feba89d39f352287@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 15723
Logged by: Anna Muravieva
Email address: ana-mur21s(at)yandex(dot)ru
PostgreSQL version: 9.6.1
Operating system: linux
Description:
Hello
We have currently that issue. "worker process died unexpectedly" was caused
by the lock on the table, which was generated because of the truncate we
use. This seems to cause the Postgres pg_dump worker process to exit
abnormally. Why this is not an Error or Warning in Postgres or pg_dump, What
we see is that pg_dump exits at this point and has not exported part of the
database. Again this feels like a Bug with Postgres or pg_dump. Could you
please help to understand
Thank you appreciated for help
Anna
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2019-03-29 10:12:47 | Re: BUG #15720: `executor could not find named tuplestore ABC` in AFTER DELETE trigger referencing OLD TABLE as ABC |
| Previous Message | PG Bug reporting form | 2019-03-29 01:14:11 | BUG #15722: 9000x performance regression on query starting PostgreSQL 10 due to bad query plan |