| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | evil-88(at)inbox(dot)ru |
| Subject: | BUG #15568: pg_dump error |
| Date: | 2018-12-28 10:26:04 |
| Message-ID: | 15568-bfe6ef6c8ab5ed46@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: 15568
Logged by: Anton1989 Anton1989
Email address: evil-88(at)inbox(dot)ru
PostgreSQL version: 10.6
Operating system: win server 2012 r2
Description:
pg_dump: large object read error 1862108: ERROR: Failed to get transaction
status 14549214
DETAIL: Could not open file "pg_clog / 000D": No such file or directory.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maxim Boguk | 2018-12-29 03:59:34 | Re: BUG #15567: Wal receiver process restart failed when a damaged wal record arrived at standby. |
| Previous Message | PG Bug reporting form | 2018-12-28 02:01:23 | BUG #15567: Wal receiver process restart failed when a damaged wal record arrived at standby. |