Re: There's some sort of race condition with the new FSM stuff - Mailing list pgsql-hackers

From Tom Lane
Subject Re: There's some sort of race condition with the new FSM stuff
Date
Msg-id 20591.1223988436@sss.pgh.pa.us
Whole thread Raw
In response to Re: There's some sort of race condition with the new FSM stuff  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: There's some sort of race condition with the new FSM stuff
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.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?   But if
there were random garbage in the forknum fields you'd expect rather more
failures than are observed.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Philip Warner
Date:
Subject: Re: Proposed patch: make pg_dump --data-only consider FK constraints
Next
From: Tom Lane
Date:
Subject: Re: Is autovacuum too noisy about orphan temp tables?