Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Error I don't understand, losing synch with server


  • From: Scott Ribe <scott_ribe(at)killerbytes(dot)com>
  • To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
  • Subject: Re: Error I don't understand, losing synch with server
  • Date: Wed, 24 May 2006 14:14:00 -0600
  • Message-id: <C09A1AA8(dot)4AFF6%scott_ribe(at)killerbytes(dot)com>

>> Every once in a while I log this error executing a query:
>> message contents do not agree with length in message type "D"
>> lost synchronization with server: got message type "O", length 1398030676
> 
> This means either that libpq got a corrupt message from the server, or
> that libpq itself contains a bug in message parsing.  Given that no one
> else has reported similar problems, the idea that your app is somehow
> clobbering the libpq message buffer (and thus corrupting the message "in
> transit") has to be taken seriously.
> 
> You mention pooling so I suppose this is a multi-threaded application
> ... are you being careful not to let any two threads try to use the same
> libpq PGconn at the same time?  libpq itself does not contain any
> locking that would make that safe, you need to provide the locking
> yourself.

Uhhhmmm, I built without --enable-thread-safety??? I have a process I follow
when building, but pg_config is telling me that I didn't use my standard
options. I'm assuming this could cause all sorts of threading kinkiness...


-- 
Scott Ribe
scott_ribe(at)killerbytes(dot)com
http://www.killerbytes.com/
(303) 722-0567 voice





Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group