| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | karol(dot)malinowski(at)trustedeyes(dot)pl |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_dump query failed |
| Date: | 2022-07-28 13:51:23 |
| Message-ID: | 3384472.1659016283@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
karol(dot)malinowski(at)trustedeyes(dot)pl writes:
> last week backup of my one database stops with error like below:
> "pg_dump: [archiver (db)] query failed: server closed the connection
> unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> Additional info:
> PostgreSQL 9.6.8 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5
> 20150623 (Red Hat 4.8.5-16), 64-bit
The first thing I'd suggest is updating to the latest release
in that branch (9.6.24). You're missing four years' worth of
bug fixes, and it's not improbable that the underlying issue
here is included in that.
If that doesn't help, you'll need to start debugging. The
symptom looks a bit like catalog corruption; if you are lucky
then REINDEX'ing the catalogs used in that query would help.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alicja Kucharczyk | 2022-07-28 14:02:00 | Re: Feature request(?): Proxy User |
| Previous Message | Ron | 2022-07-28 13:47:52 | Re: pg_dump query failed |