Re: 7.1.1 backend crashes on updates to very large text columns - Mailing list pgsql-general

From Norman J. Clarke
Subject Re: 7.1.1 backend crashes on updates to very large text columns
Date
Msg-id Pine.LNX.4.21.0105281051580.9920-100000@norman-comp.combimatrix.com
Whole thread Raw
In response to Re: 7.1.1 backend crashes on updates to very large text columns  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hello Tom,

While you were busy responding (should have checked email sooner!) my
coworker helped me go through the core file and we found the exact
problem, which was of course what you pointed out. A little wasted time
maybe, but it was neat to see what was really going on. Thanks very much
for getting back to me so quickly!

Norm

--------------------------------------
Norman Clarke
Combimatrix Corp Software Development
Harbour Pointe Tech Center
6500 Harbour Heights Pkwy, Suite 301
Mukilteo, WA 98275

tel: 425.493.2240
fax: 425.493.2010
--------------------------------------

On Tue, 29 May 2001, Tom Lane wrote:

> "Norman J. Clarke" <norman@combimatrix.com> writes:
> > However, on update to the larger (100k+)columns, the postgres backend
> > crashes and dumps core. I've included a backtrace from the core file.
>
> This looks entirely irrelevant to either TOAST or update; I think it is
> the known 7.1.1 bug with SELECTs that return no rows in plpgsql.
> Try 7.1.2.
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>


pgsql-general by date:

Previous
From: "Eric G. Miller"
Date:
Subject: Re: incomplete transaction keeps table locked?
Next
From: Denis Gasparin
Date:
Subject: Re: Kylix, dbexpress & PostgreSql