Re: BUG #4567: Clustering on GIST INDEX clobbers records in table intermittently

From: "Obe, Regina" <robe(dot)dnd(at)cityofboston(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-bugs(at)postgresql(dot)org>, <postgis-devel(at)postgis(dot)refractions(dot)net>
Subject: Re: BUG #4567: Clustering on GIST INDEX clobbers records in table intermittently
Date: 2008-12-08 07:51:09
Message-ID: 53F9CF533E1AA14EA1F8C5C08ABC08D204D7F07A@ZDND.DND.boston.cob
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Regina Obe" <robe(dot)dnd(at)cityofboston(dot)gov> writes:
> Description: Clustering on GIST INDEX clobbers records in table
> intermittently

> This doesn't always happen to me but does intermittently, and for others it
> happens all the time.

> I wonder whether this is fixed by this recent patch:
> http://archives.postgresql.org/pgsql-committers/2008-12/msg00053.php

> The pre-patch behavior would've depended on the value of a
> never-initialized struct field, so the erratic behavior is explained
> by varying contents of memory. I'm unable to make it happen in an
> assert-enabled build, but that's probably because the initial contents
> of a palloc'd chunk are never zeroes in such a build.

> regards, tom lane

Tom,

Thanks for the quick response on this.

Paul,
You think by chance you can test out the patch since you can make this bug happen consistently on your build.

Thanks,
Regina

-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Sameer Mahajan 2008-12-08 13:04:24 BUG #4568: sporadic error doing COUNT(*) on empty table
Previous Message Tom Lane 2008-12-08 02:09:35 Re: BUG #4564: multi threaded queries corrupt client when server debugging levels are hi