From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Mount <petermount@it.maidstone.gov.uk>
Cc: 'M.Mazurek@poznan.multinet.pl' <M.Mazurek@poznan.multinet.pl>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] invalid lo descriptorc in begin commit fraze
Date: Wed, 16 Feb 2000 10:10:41 -0500
Message-ID: <2770.950713841@sss.pgh.pa.us> (raw)
In-Reply-To: <1B3D5E532D18D311861A00600865478C70C1E9@exchange1.nt.maidstone.gov.uk>
References: <1B3D5E532D18D311861A00600865478C70C1E9@exchange1.nt.maidstone.gov.uk>
Peter Mount <petermount@it.maidstone.gov.uk> writes:
> I'll look into it. There shouldn't be anything in the driver to limit
> the number of concurrent objects.
> Does anyone else see this type of problem (I'm thinking of those who use
> libpq rather than JDBC)?
I got the impression that what he was talking about was multiple
independent threads issuing commands across a single backend connection.
When one thread commits its transaction, all the others lose their open
LO descriptors. I don't see any way to fix that short of changing the
client code so that each thread is talking to a different backend.
If I'm all wrong about this, I'll crawl back in my hole now...
regards, tom lane
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: tgl@sss.pgh.pa.us, petermount@it.maidstone.gov.uk, M.Mazurek@poznan.multinet.pl
Subject: Re: [INTERFACES] invalid lo descriptorc in begin commit fraze
In-Reply-To: <2770.950713841@sss.pgh.pa.us>
* 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