Re: pg_dump's results have quite different size

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(dot)shulgin(at)zalando(dot)de> wrote:

> On Dec 14, 2016 06:01, "Kaijiang Chen" <chenkaijiang(at)gmail(dot)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
>
>