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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>, 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:53:16
Message-ID: 12687.1224013996@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> Zdenek Kotala wrote:
>> Tom Lane napsal(a):
>>> 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.

Yeah, but the observed symptoms seem to indicate that the fill is mostly
zeroes with a very occasional one. This seems less than probable.

The only theory I've thought of that seems to fit the facts is that
someplace we have a wild store that is clobbering that particular word.
Which is a pretty unpleasant thought.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2008-10-14 20:02:56 Re: There's some sort of race condition with the new FSM stuff
Previous Message David E. Wheeler 2008-10-14 19:50:43 Re: spoonbill is failing citext test