From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | prakash(dot)ramakrishnan(dot)ap(at)nielsen(dot)com |
Subject: | BUG #15401: pg_dump error |
Date: | 2018-09-25 15:54:41 |
Message-ID: | 15401-e328bb0871b850b0@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: 15401
Logged by: prakash
Email address: prakash(dot)ramakrishnan(dot)ap(at)nielsen(dot)com
PostgreSQL version: 9.6.6
Operating system: Red Hat Enterprise Linux Server release 7.4 (Maipo
Description:
Hi Team ,
While am connecting the standby server to taking the backup getting below
error.
==> pg_dump -h LHRRHENPPP002.enterprisenet.org -p 5432 -d AIUK01PR -U
postgres -Fd -f /PGDATA/prakash_backup/AIUK01PR.sql
Password:
pg_dump: Dumping the contents of table "cmt_attributes" failed:
PQgetResult() failed.
pg_dump: Error message from server: ERROR: canceling statement due to
conflict with recovery
DETAIL: User was holding a relation lock for too long.
pg_dump: The command was: COPY cmtroi_owner.cmt_attributes (id, cmt_id,
user_id, insert_date, last_change_date, height, width, duration, dpi,
filesize, codec) TO stdout;
Regards,
Prakash.R
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2018-09-25 16:45:23 | Re: BUG #15401: pg_dump error |
Previous Message | PG Bug reporting form | 2018-09-25 12:07:23 | BUG #15400: perl error |