Re: [HACKERS] libpq lo_open errors when first action in connection

2005-05-13 Thread Greg Sabino Mullane
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The problem is that LO descriptors are only valid for the duration of the transaction. Thanks, that's it all right. I forgot to update the lo_ stuff when we switched the autocommit mojo around a while back. I think you should make the func()

[HACKERS] libpq lo_open errors when first action in connection

2005-05-12 Thread Greg Sabino Mullane
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm having some problems with lo_open inside of DBD::Pg (which uses libpq) and need help in debugging the problem. The problem is that a call to lo_open works perfectly, *unless* it is the first thing that this connection to the database has done,

Re: [HACKERS] libpq lo_open errors when first action in connection

2005-05-12 Thread Alvaro Herrera
On Fri, May 13, 2005 at 02:39:25AM -, Greg Sabino Mullane wrote: I'm having some problems with lo_open inside of DBD::Pg (which uses libpq) and need help in debugging the problem. The problem is that a call to lo_open works perfectly, *unless* it is the first thing that this connection to

Re: [HACKERS] libpq lo_open errors when first action in connection

2005-05-12 Thread Tom Lane
Greg Sabino Mullane [EMAIL PROTECTED] writes: I'm having some problems with lo_open inside of DBD::Pg (which uses libpq) and need help in debugging the problem. lo_open doesn't work unless inside a transaction block (and even if it did work, the result would be useless to you). I believe the