From: | Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de> |
---|---|
To: | 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-14 09:09:41 |
Message-ID: | CACACo5QRXyxKc6hm=mDNAQeS=bWa99u8odAGVv_mGEqNephPXQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Dec 14, 2016 at 9:29 AM, Kaijiang Chen <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.
--
Alex
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-12-14 15:00:52 | Re: BUG #14466: can with recursive query add LOOPth variable? |
Previous Message | Kaijiang Chen | 2016-12-14 08:29:27 | Re: pg_dump's results have quite different size |