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

2007-01-17 Thread Martijn van Oosterhout
On Wed, Jan 17, 2007 at 05:34:27PM -0500, Tom Lane wrote: > Sterpu Victor <[EMAIL PROTECTED]> 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 violat

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

2007-01-17 Thread Tom Lane
Sterpu Victor <[EMAIL PROTECTED]> 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 se

[GENERAL] FATAL: invalid frontend message type 47 server closed the connection unexpectedly

2007-01-17 Thread Sterpu Victor
I receive this message when I do a specific operation. How can I debug something like this? I use a Centos 4.0 distribution, postgresql version 8.1.3(I also used diffrent distibutions and other versions of postgresql). I connect to postgresql using perl DBD::Pg, using a tcp socket. The error a

Re: [GENERAL] FATAL: invalid frontend message type 47

2006-01-24 Thread Michael Fuhr
On Tue, Jan 24, 2006 at 11:50:39PM -0500, Sterpu Victor wrote: > After a commit I receive this message: > "FATAL: invalid frontend message type 47", and rollback. The client seems to have violated the communications protocol. What client interface are you using? What version of PostgreSQL (both

[GENERAL] FATAL: invalid frontend message type 47

2006-01-24 Thread Sterpu Victor
After a commit I receive this message: "FATAL: invalid frontend message type 47", and rollback. ---(end of broadcast)--- TIP 6: explain analyze is your friend