Re: Error while using pg_dump - Mailing list pgsql-general

From David Rowley
Subject Re: Error while using pg_dump
Date
Msg-id CAKJS1f_+hx=jd97PXi_Nw3CaNTnM8sMSYw4nnTLN4ULtLiuHEg@mail.gmail.com
Whole thread Raw
In response to Error while using pg_dump  (Raghavendra Rao J S V <raghavendrajsv@gmail.com>)
Responses Re: Error while using pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Tue, 16 Apr 2019 at 20:43, Raghavendra Rao J S V
<raghavendrajsv@gmail.com> wrote:
> We are facing below error while taking the backup of the database using pg_dump. Could you suggest me how to rectify
this?
>
> pg_dump: [archiver (db)] query was: COPY public.aclappliedtopep (id, instance_version, direction, aclname, ifname,
owningentityid,protocolendpoint_id, deploypending, authentityid, authentityclass, accesscontrollist_id) TO stdout;
 
>
> dollar qustion is 1
>
> dbuser name is qovr , dbname is qovr and direcotry is
/opt/tempbackups/HCS-SYD3-PCA01-weekly-backup/backup/appcomponent/qovr-db/emms_db_09_05_17_18_46_26.dump
>
> dollar qustion is 0
>
> pg_dump: FATAL:  terminating connection due to administrator command
>
> pg_dump: [archiver (db)] query failed: server closed the connection unexpectedly
>
>                 This probably means the server terminated abnormally
>
>                 before or while processing the request.
>
> pg_dump: [archiver (db)] query was: COPY public.aclappliedtopep (id, instance_version, direction, aclname, ifname,
owningentityid,protocolendpoint_id, deploypending, authentityid, authentityclass, accesscontrollist_id) TO stdout;
 

This looks very much like the backend crashed as a result of the COPY.
Can you share which version of PostreSQL you're getting this with? If
not the latest minor version for the release, does it still happen on
the latest?

It would also be good if you could see if you could recreate the crash
with using:

COPY (SELECT * FROM public.aclappliedtopep) TO stdout;

then if you can, try to narrow down if it's crashing because of some
record by either adding a WHERE clause to the SELECT, or perhaps a
LIMIT.  If for example, you can get it to crash with LIMIT 1, can you
send us the psql output of \d public.aclappliedtopep and also some
anonymised version of the row it crashes on? (ensuring it still
crashes once anonymised). You may be able to narrow it down by "binary
searching" through various LIMIT / OFFSET combinations.

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services



pgsql-general by date:

Previous
From: Tim Kane
Date:
Subject: Alter domain type / avoiding table rewrite
Next
From: Tom Lane
Date:
Subject: Re: Error while using pg_dump