Re: [HACKERS] Re: SIGBUS in AllocSetAlloc & jdbc - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Re: SIGBUS in AllocSetAlloc & jdbc
Date
Msg-id 13559.925665130@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Re: SIGBUS in AllocSetAlloc & jdbc  (Tatsuo Ishii <t-ishii@sra.co.jp>)
Responses Re: [HACKERS] Re: SIGBUS in AllocSetAlloc & jdbc
List pgsql-hackers
Tatsuo Ishii <t-ishii@sra.co.jp> writes:
> So far I couldn't find nothing special with the backend by now. Going
> back to the ImageViewer, I think I found possible problem with it. In
> my understanding, every lo call should be in single transaction block. 
> But ImageViwer seems does not give any "begin" or "end" SQL commands.
> I made a small modifications(see below patches) to the ImageViewer and
> now it starts to work again with 6.5 backend!

Hmm.  The documentation does say somewhere that LO object handles are
only good within a transaction ... so it's amazing this worked reliably
under 6.4.x.

Is there any way we could improve the backend's LO functions to defend
against this sort of misuse, rather than blindly accepting a stale
filehandle?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: [HACKERS] Re: SIGBUS in AllocSetAlloc & jdbc
Next
From: Tom Lane
Date:
Subject: GROUP BY fixes committed