From: | bricklen <bricklen(at)gmail(dot)com> |
---|---|
To: | |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: unexpected message type 0x58 during COPY from stdin |
Date: | 2010-08-26 16:09:54 |
Message-ID: | AANLkTi=v0hKhCt+vTXHMPeuQ=wsRBi70bJKU2x+OwmYf@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Aug 25, 2010 at 12:20 PM, bricklen <bricklen(at)gmail(dot)com> wrote:
> On Wed, Aug 25, 2010 at 12:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>
>> bricklen <bricklen(at)gmail(dot)com> writes:
>> > I'm getting a strange error during reload of one of our databases.
>>
>> This appears to indicate that the server's first idea that there was
>> trouble came when the client side disconnected partway through a COPY:
>>
>> > 2010-08-25 04:16:46 PDT [2401]: [1-1] (user=postgres) ERROR: unexpected
>> > message type 0x58 during COPY from stdin
>>
>> (0x58 = 'X' = Terminate message, implying client called PQfinish)
>>
>> So it would be useful to look at what pg_restore thinks happened.
>> I rather suspect your cron setup sends pg_restore's output to
>> /dev/null ... or at least you failed to show it.
>>
>> regards, tom lane
>
>
> cron:
>
> MAILTO=""
>
> 30 2 * * * /var/lib/pgsql/sync-db.sh 2>&1
>
> I'll modify that to append to a log file and see what else turns up.
>
FWIW, the output to a logfile from the cron was minimal and didn't
show anything new. I'm going to try it again tomorrow starting a
couple hours later, to rule out some odd 4am-ish problem that affects
the cron jobs.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-08-26 16:29:23 | Re: looping on NEW and OLD in a trigger |
Previous Message | Guy Rouillier | 2010-08-26 16:00:05 | Re: IBATIS support for postgres cursors |