From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Seth Nickell <snickell(at)stanford(dot)edu> |
Cc: | greg(at)turnstep(dot)com, pgsql-novice(at)postgresql(dot)org |
Subject: | Re: libpg: large object problems |
Date: | 2003-05-04 00:18:34 |
Message-ID: | 19956.1052007514@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Seth Nickell <snickell(at)stanford(dot)edu> writes:
> If I only put one lo_ operation per transaction, I get back "0" for the
> fd (is this a valid fd?). I guess this is an improvement over -1 ;-) It
> seems I can do an lo_write at this point, but lo_read still doesn't let
> me read anything.
I think the lo_open() for reading needs to specify INV_READ.
An error that may or may not be hurting you is that the lo_close in
the write part should specify fd not id. It is possible that that
mistake is making the writer transaction abort. The lack of checks
for errors makes it difficult to tell, but you could possibly look
in the postmaster log for clues...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | greg | 2003-05-04 01:05:23 | Re: libpg: large object problems |
Previous Message | Nabil Sayegh | 2003-05-03 23:00:11 | Re: Error Uninstalling 7.2.2 on Mandrake 9.0 |