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

From Brian P Millett
Subject Re: [HACKERS] Re: SIGBUS in AllocSetAlloc & jdbc
Date
Msg-id 373870DE.7A63FC06@ec-group.com
Whole thread Raw
In response to Re: [HACKERS] Re: SIGBUS in AllocSetAlloc & jdbc  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List pgsql-hackers
Tatsuo Ishii wrote:

> > This is all clearly part of the large object mess that we were in before
> > you fixed large objects.
> >
> > Do whatever you think is best for the long term.  Large objects were so
> > terribly fragile in previous releases, we might as well advertise them
> > again as now working 100% of the time.  If the new behaviour changes
> > existing apps, that is OK if the new behaviour is superior.  They will
> > be thrilled to change their apps if the large object system now works
> > better.
> >
> > It would be different if the old system worked properly.
>
> I have changed lo_read/lo_write so that they run under same memory
> context as other LO calls.

Well, for the first time (for me) the blobtest.java now works correctly.

That would be Solaris 2.7, cvs checkout 19990511, jdk1.2.1_02.

Thank you all for the great work.

--
Brian Millett
Enterprise Consulting Group     "Heaven can not exist,
(314) 205-9030                     If the family is not eternal"
bpm@ec-group.com                   F. Ballard Washburn





pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] More on GROUP BY
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Re: [SQL] plpgsql error