unexpected message type 0x58 during COPY from stdin - Mailing list pgsql-general

From bricklen
Subject unexpected message type 0x58 during COPY from stdin
Date
Msg-id AANLkTim6FfS7cTptX7bFgy5DZAQr6ythbU9Z8nJfcJNt@mail.gmail.com
Whole thread Raw
Responses Re: unexpected message type 0x58 during COPY from stdin
Re: unexpected message type 0x58 during COPY from stdin
List pgsql-general
Hello,

I'm getting a strange error during reload of one of our databases. For the past several weeks, we have been seeing the following error regularly, but not necessarily with the same table. The pg_restore aborts after this error, resulting in an incomplete reload. At first I thought it might be related to our upgrade to 8.4.4 several weeks ago so we downgraded to 8.4.2, but the error still occurs. Interestingly, if I run the restore command manually (from the command line), it works fine -- only in cron does it fail.

uname -a
Linux ike.nbinternal.com 2.6.18-164.6.1.el5 #1 SMP Tue Nov 3 16:12:36 EST 2009 x86_64 x86_64 x86_64 GNU/Linux

version()
PostgreSQL 8.4.2 on x86_64-redhat-linux-gnu, compiled by GCC gcc (GCC) 4.1.2 20071124 (Red Hat 4.1.2-42), 64-bit

-- dump file is created with:
pg_dump --format=custom $DATABASE $EXCLUDE_TABLES > ~/backups/daily-backup.dump

-- restore command:

pg_restore -d nbaffnet -F c -j 4 -v -C --no-data-for-failed-tables /var/lib/pgsql/daily-backup.dump


-- error:
2010-08-25 04:16:46 PDT [2401]: [1-1] (user=postgres) ERROR:  unexpected message type 0x58 during COPY from stdin
2010-08-25 04:16:46 PDT [2401]: [2-1] (user=postgres) CONTEXT:  COPY afffraud, line 1
2010-08-25 04:16:46 PDT [2401]: [3-1] (user=postgres) STATEMENT:  COPY afffraud (id, idaff, maxkey, maxvalue) FROM stdin;
2010-08-25 04:16:46 PDT [2401]: [4-1] (user=postgres) LOG:  could not send data to client: Broken pipe
2010-08-25 04:16:46 PDT [2401]: [5-1] (user=postgres) STATEMENT:  COPY afffraud (id, idaff, maxkey, maxvalue) FROM stdin;
2010-08-25 04:16:46 PDT [2401]: [6-1] (user=postgres) LOG:  unexpected EOF on client connection

Note: we have been doing these backups and restores for at least a year and a half without any problems, and we can't think of anything that might have changed.


Cheers,

Bricklen

pgsql-general by date:

Previous
From: "A.M."
Date:
Subject: initdb fails to allocate shared memory
Next
From: "Joshua D. Drake"
Date:
Subject: Re: initdb fails to allocate shared memory