Re: There's some sort of race condition with the new FSM stuff

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, books(at)ejurka(dot)com
Subject: Re: There's some sort of race condition with the new FSM stuff
Date: 2008-10-14 19:35:15
Message-ID: 48F4F473.6090707@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Zdenek Kotala wrote:
> Tom Lane napsal(a):
>> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>>> I still wonder, though, why we're seeing the error consistently on
>>> kudu, and not on any other animal. Perhaps the forknum field that's
>>> left uninitialized gets a different value there than on other platforms.
>>
>> Hmm ... AFAICS this mistake would mean that no forknum field of the
>> requests[] array ever gets set at all, so they would stay at whatever
>> the virgin value in the shmem segment had been. Perhaps Solaris doesn't
>> guarantee that a shared memory block starts out as zeroes?
>
> For security reason any OS should clean memory pages before process
> first touches them.

Yeah. But it doesn't necessarily need to fill them with zeros, any
garbage will do.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2008-10-14 19:36:03 spoonbill is failing citext test
Previous Message Bruce Momjian 2008-10-14 19:16:30 Re: Updates of SE-PostgreSQL 8.4devel patches