7.3.2 client connecting to 7.2.1 server problem

[Jeff]

I have the following packages installed on my system:

libpq3: 7.3.2r1-5
python-pygresql: 7.3.2r1-5
postgresql: 7.2.1-2woody2
postgresql-client: 7.2.1-2woody2

In my application, which is written in python, I get a "server closed the
connection unexpectedly" exception after executing a few sql commands. I
print each query before I execute it (debugging) so I tried executing the
queries through psql with no problems.

Is there a known incompatibility between the versions of client/server that
I'm using? Or a known bug in pygresql?

I tried looking for an option to turn on query logging (I thought one was
present), but for some reason I didn't notice it. Is there a way to log
queries without restarting the server? It's a little troublesome for me to
start and stop the server (it's a production server), but I will if
necessary.

Here are the queries that execute (field names have been obfuscated):
BEGIN;
SELECT active FROM process WHERE xx='aa' FOR UPDATE;
UPDATE process SET active='t' WHERE xx='aa';
COMMIT;
-- server dies while trying to execute query below
SELECT bb.id as id,first,last,t ype from bb,cc where bb.id=bb_id order by dd
asc limit 1;

Sometimes, strangely, it makes it to a point further in the application but
crashes there instead one a different query (all the same program inputs).
I can't reproduce this result, although I recall it happening twice.

I've been using all that software together for quite some time with no
problems until now.

Any advice is appreciated.

Regards,
Jeff

[Tom Lane]

Jeff <as**@asdf.co m> writes:

I have the following packages installed on my system:
libpq3: 7.3.2r1-5
python-pygresql: 7.3.2r1-5
postgresql: 7.2.1-2woody2
postgresql-client: 7.2.1-2woody2 In my application, which is written in python, I get a "server closed the
connection unexpectedly" exception after executing a few sql commands.

Hmm. What do you see in the postmaster log when this happens?

BTW, you *really* should update to 7.2.4. There are nasty bugs in
7.2.1. There's not enough info here to guess whether you are hitting
a known bug, though.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

[Oliver Elphick]

On Wed, 2003-09-17 at 21:55, Jeff wrote:

I have the following packages installed on my system:

libpq3: 7.3.2r1-5
python-pygresql: 7.3.2r1-5
postgresql: 7.2.1-2woody2
postgresql-client: 7.2.1-2woody2
[This is clearly a Debian system.]
You seem to have done a partial upgrade to testing; the effect will be
that you have two versions of the libpq library, and python-pygresql
will not be using the same one as pgsql. It looks as though I made the
dependencies too loose in that testing release.
In my application, which is written in python, I get a "server closed the
connection unexpectedly" exception after executing a few sql commands. I
print each query before I execute it (debugging) so I tried executing the
queries through psql with no problems.

Is there a known incompatibility between the versions of client/server that
I'm using? Or a known bug in pygresql?

I suggest you upgrade to the version from unstable (7.3.4-5). Testing
is held up and isn't getting timely upgrades; I would not, myself,
consider it as good as unstable until we get very close to a new Debian
release.

Unstable has versioned python packages. If you want woody versions of
the postgresql packages, you can get them with this apt line:

deb http://people.debian.org/~elphick/debian main

--
Oliver Elphick Ol************@ lfix.co.uk
Isle of Wight, UK http://www.lfix.co.uk/oliver
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C
=============== =============== ==========
"But my God shall supply all your need according to his
riches in glory by Christ Jesus." Philippians 4:19
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddres sHere" to ma*******@postg resql.org)