Skip site navigation (1) Skip section navigation (2)

Re: [postgis-devel] RE: BUG #4567: Clustering on GIST INDEX clobbers records in table intermittently

From: "Paul Ramsey" <pramsey(at)cleverelephant(dot)ca>
To: "PostGIS Development Discussion" <postgis-devel(at)postgis(dot)refractions(dot)net>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: [postgis-devel] RE: BUG #4567: Clustering on GIST INDEX clobbers records in table intermittently
Date: 2008-12-08 19:02:08
Message-ID: 30fe546d0812081102q53f5ff58of75d74b8ea5c13c@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Yes, that patch removes the bug.

P.

On Sun, Dec 7, 2008 at 11:51 PM, Obe, Regina <robe(dot)dnd(at)cityofboston(dot)gov> wrote:
> "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.
>
> ________________________________
>
> Help make the earth a greener place. If at all possible resist printing this
> email and join us in saving paper.
>
> _______________________________________________
> postgis-devel mailing list
> postgis-devel(at)postgis(dot)refractions(dot)net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>
>

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2008-12-08 21:31:41
Subject: Re: BUG #4565: nextval not updated during wal replication, leading to pk violations
Previous:From: Marc SchablewskiDate: 2008-12-08 17:14:14
Subject: Re: BUG #4565: nextval not updated during wal replication, leading to pk violations

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group