Re: [GENERAL] invalid frontend message type 136

2013-09-11 Thread Steve Crawford
On 09/10/2013 11:30 AM, David Johnston wrote: Steve Crawford wrote 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 connect

Re: [GENERAL] invalid frontend message type 136

2013-09-10 Thread David Johnston
Steve Crawford wrote > 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 lig

Re: [GENERAL] invalid frontend message type 136

2013-09-10 Thread Steve Crawford
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 cr

[GENERAL] invalid frontend message type 136

2013-09-05 Thread Steve Crawford
I got this message immediately after a connection to the server. I haven't seen it before and Googling has come up short so far. There are no other indications of trouble. Ideas or suggestions where to look? Cheers, Steve -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org)

Re: [GENERAL] invalid frontend message type 136

2013-09-05 Thread David Johnston
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: