Postgres Pro
Downloads
Home   >   mailing lists

Re: [BUGS] pg_dump's results have quite different size - Mailing list pgsql-bugs

From Kaijiang Chen
Subject Re: [BUGS] pg_dump's results have quite different size
Date
Msg-id CAAkGvS_aTgMuqh7_VGB+U0q0yC6wYLzOTSREog=yyyQkmFbDPA@mail.gmail.com
Whole thread Raw
In response to Re: [BUGS] pg_dump's results have quite different size  (Oleksandr Shulgin <oleksandr.shulgin@zalando.de>)
Responses Re: [BUGS] pg_dump's results have quite different size
List pgsql-bugs
Tree view
Yes. The pg_dump quits with the message:

pg_dump: Dumping the contents of table "data_histories" failed: PQgetResult() failed.
pg_dump: Error message from server: ERROR:  canceling statement due to conflict with recovery
DETAIL:  User query might have needed to see row versions that must be removed.
pg_dump: The command was: COPY public.data_histories (id, user_id, user_name, type, type_id, old_data, action, new_data, created_at, updated_at) TO stdout;


On Wed, Dec 14, 2016 at 4:23 PM, Oleksandr Shulgin <oleksandr.shulgin@zalando.de> wrote:
On Dec 14, 2016 06:01, "Kaijiang Chen" <chenkaijiang@gmail.com> wrote:
I found that it is because I run the pg_dump on standby and it conflicts with the stream replication. I enlarge the max_standby_streaming_delay. It should work.

Does the conflict cause a fatal error on the pg_dump side?

--
Alex


pgsql-bugs by date:

Previous
From: Oleksandr Shulgin
Date:
Subject: Re: [BUGS] pg_dump's results have quite different size
Next
From: Oleksandr Shulgin
Date:
Subject: Re: [BUGS] pg_dump's results have quite different size