On 14/12/16 22:09, Oleksandr Shulgin wrote:
> On Wed, Dec 14, 2016 at 9:29 AM, Kaijiang Chen <chenkaijiang@gmail.com
> <mailto:chenkaijiang@gmail.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
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs