Re: Backend crash while indexing large strings - Mailing list pgsql-bugs

From Stephen van Egmond
Subject Re: Backend crash while indexing large strings
Date
Msg-id 20010208180726.A21674@bang.dhs.org
Whole thread Raw
In response to Re: Backend crash while indexing large strings  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tom Lane (tgl@sss.pgh.pa.us) wrote:
> I get
>
> FATAL 1:  btree: failed to add item to the page in _bt_sort (2)
> pqReadData() -- backend closed the channel unexpectedly.
>         This probably means the backend terminated abnormally
>         before or while processing the request.
>
> Is that the same thing you see?

Yes, sorry for omitting the crash.

> The script does not seem to trigger the failure in current sources,
> so I suspect the equal-keys changes I made awhile back fixed it.
> But I will dig into the crash and make sure.  Many thanks for providing
> a self-contained test case!

Great!  Excellent.  Looking forward to 7.1!

Having just spent last night (midnight to 4 am) installing Oracle, let
me say that I'm going to make my positive best efforts to work with
pgsql.

I was considering using the ACS (http://www.arsdigita.com/ ),
which requries Oracle, but after last night's nightmare, I'm hereby
pledging to work with OpenACS (http://www.openacs.org/ ) which is
a port to Postgres.

/Steve

pgsql-bugs by date:

Previous
From: "Constantin Teodorescu"
Date:
Subject: Re: Problem displaying functions and views in 7.1b3
Next
From: "praveenkumar reddy m"
Date:
Subject: please give me the answer