Re: [HACKERS] Re: SIGBUS in AllocSetAlloc & jdbc

From: Brian P Millett <bpm(at)ec-group(dot)com>
To: t-ishii(at)sra(dot)co(dot)jp
Cc: postgres <hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] Re: SIGBUS in AllocSetAlloc & jdbc
Date: 1999-05-11 18:03:11
Message-ID: 373870DE.7A63FC06@ec-group.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)ec-group(dot)com F. Ballard Washburn

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-05-11 18:08:04 Re: [HACKERS] Re: [SQL] plpgsql error
Previous Message Bruce Momjian 1999-05-11 18:01:31 Re: [HACKERS] More on GROUP BY