2005-04-02 00:09:01 ERROR: invalid string enlargement request size
1358954492
2005-04-02 00:09:01 WARNING: AbortTransaction and not in in-progress
state
2005-04-02 00:09:01 FATAL: invalid frontend message type 82
This indicates the client code didn't follow the protocol properly,
ie, it sent garbage where a message length word ought to be.
This sort of thing has been seen to occur when multiple client-side
threads try to use the same database connection without proper locking
to ensure only one thread uses it at a time. See for example
http://archives.postgresql.org/pgsql-hackers/2004-09/msg00104.php
regards, tom lane
This is exactly what I am doing. Must admit I haven't considered that as an issue.
For performance reasons I suppose one database connection per client are preferred
rather than using synchronized on the db class ?
Thanks a lot for bringing it to my attention
BR, Poul
