From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
---|---|
To: | Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>, Kaijiang Chen <chenkaijiang(at)gmail(dot)com> |
Cc: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: pg_dump's results have quite different size |
Date: | 2016-12-16 07:18:38 |
Message-ID: | 3b9af4ce-edba-0006-43a0-31ce6d7624f5@catalyst.net.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 14/12/16 22:09, Oleksandr Shulgin wrote:
> On Wed, Dec 14, 2016 at 9:29 AM, Kaijiang Chen <chenkaijiang(at)gmail(dot)com
> <mailto:chenkaijiang(at)gmail(dot)com>> wrote:
>
> 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;
>
>
> Ah, then it's just that your backup script is broken: it should have
> reported the error.
>
> Please do not top-post.
Oleksandr - how about a helpful response? E.g suggesting that maybe
increasing max_standby_streaming_delay might help? Goddamn! folk asking
for help deserve better than just being told 'it is broken dickhead'...
This open src stuff originally started as a way for us all to *help*
each other, let's not forget that!
regards
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Rahul Kumar | 2016-12-16 09:08:41 | Re: BUG #14467: Insertion Issue with Hibernate |
Previous Message | Johannes Lochmann | 2016-12-15 13:46:19 | Re: BUG #14467: Insertion Issue with Hibernate |