From: Mihnea Balta <dark@dark.vodanet.ro>
To: pgsql-interfaces@postgresql.org
Subject: Libpq lock up
Date: Sun, 14 Apr 2002 13:56:58 +0300
Message-ID: <200204141356.58031.dark@dark.vodanet.ro> (raw)
Hi.
I'm using libpq in several apps. If I keep a connection open for a long time
(hours) and pass a large amount of queries through it, it finally locks in a
select() syscall. I'm freeing the previous result set (if it exists) before
making a new query, so I suppose it's not an out-of-memory/handles problem.
My platform used to be linux 2.4.9 / glibc 2.1.3 / postgres 7.2.1.
Now I've moved postgres on a linux 2.4.18 / glibc 2.2.3, but in the mean time
I modified my apps to buffer stuff and connect to the database each time they
need to perform a query, so I don't know if upgrading glibc solved the
problem.
Has anyone encountered a simmilar problem so far? Now I've got to write an app
that performs a fair amount of queries and I'd rather not disconnect/connect
to the backend for each one of them. Buffering is not well seen in this case
either, because loosing buffered data due to an application crash is bad
karma.
Thanks in advance ;)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: dark@dark.vodanet.ro
Subject: Re: Libpq lock up
In-Reply-To: <200204141356.58031.dark@dark.vodanet.ro>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox