Yes, that patch removes the bug.
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
>> This doesn't always happen to me but does intermittently, and for others
>> happens all the time.
>> I wonder whether this is fixed by this recent patch:
>> 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
> Thanks for the quick response on this.
> You think by chance you can test out the patch since you can make this bug
> happen consistently on your build.
> 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
> 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
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2008-12-08 21:31:41|
|Subject: Re: BUG #4565: nextval not updated during wal replication, leading to pk violations |
|Previous:||From: Marc Schablewski||Date: 2008-12-08 17:14:14|
|Subject: Re: BUG #4565: nextval not updated during wal replication,
leading to pk violations|