Re: invalid frontend message type 136

Sorry, I should have included that. The error occurred when an older
client running 8.3.7 (I know, ferreting and finishing upgrades on
clients with old libraries is in progress) on CentOS 5.3 (32-bit). Of
all the machines connecting to the server, this one pretty lightly
loaded and typically creates a new connection to the server somewhat
over 10,000 times/week. This is the first instance of the error.

These machines/connections are buried behind firewalls in an automated
system and this particular connection is password-less.

The server is PostgreSQL 9.1.9 on x86_64-unknown-linux-gnu, compiled by
gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3, 64-bit.

Cheers,
Steve


On 09/05/2013 12:04 PM, David Johnston wrote:
> It would help to at least know against which version of the database you are
> trying to connect and also what client (with version) you are using.  Any
> other connection-related information (password based; ident; etc...) would
> be helpful as well.
>
> David J.
>
>
>
>
> --
> View this message in context:
http://postgresql.1045698.n5.nabble.com/invalid-frontend-message-type-136-tp5769775p5769778.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
>