Re: FATAL: invalid frontend message type 47 server closed the connection unexpectedly

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Sterpu Victor <victor(at)ambra(dot)ro>, pgsql-general(at)postgresql(dot)org
Subject: Re: FATAL: invalid frontend message type 47 server closed the connection unexpectedly
Date: 2007-01-18 06:15:10
Message-ID: 20070118061510.GA29963@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jan 17, 2007 at 05:34:27PM -0500, Tom Lane wrote:
> Sterpu Victor <victor(at)ambra(dot)ro> writes:
> > I receive this message when I do a specific operation.
> > How can I debug something like this?
>
> It sounds like DBD::Pg is sending an invalidly formed message, or in
> some other way violating the protocol. Or maybe the backend got
> confused. Watching the session with a packet-sniffer would help to
> nail down who's at fault.

Well, DBD::Pg merely uses libpq. The most likely issue is somethong
that's not allowed, like using the same connection from multiple
threads. Or some other break in protocol.

We're going to need a lot more info to work this out. Incidently, 47 is
a capital G, IIRC.

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2007-01-18 06:19:21 Re: datatype advice numeric vs. varchar
Previous Message Gene 2007-01-18 06:15:02 datatype advice numeric vs. varchar