Re: [GENERAL] unexpected message type 0x58 during COPY from stdin

2010-08-26 Thread bricklen
On Wed, Aug 25, 2010 at 12:20 PM, bricklen wrote: > On Wed, Aug 25, 2010 at 12:01 PM, Tom Lane wrote: >> >> bricklen 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

Re: [GENERAL] unexpected message type 0x58 during COPY from stdin

2010-08-25 Thread bricklen
On Wed, Aug 25, 2010 at 12:01 PM, Tom Lane wrote: > > bricklen 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: > > > 201

Re: [GENERAL] unexpected message type 0x58 during COPY from stdin

2010-08-25 Thread Tom Lane
bricklen 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: unexpe

Re: [GENERAL] unexpected message type 0x58 during COPY from stdin

2010-08-25 Thread bricklen
On Wed, Aug 25, 2010 at 8:35 AM, Thom Brown wrote: > > > Just seeking the obvious, but is the file you've shown being output > with pg_dump the same one you're using on pg_restore? The paths are > different, although if that's on 2 different machines, that would make > perfect sense. > > -- > Th

Re: [GENERAL] unexpected message type 0x58 during COPY from stdin

2010-08-25 Thread Thom Brown
On 25 August 2010 16:25, bricklen wrote: > 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 i

[GENERAL] unexpected message type 0x58 during COPY from stdin

2010-08-25 Thread bricklen
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 b