Postgres Pro
Downloads
Home   >   mailing lists

Re: pgsql: Do all accesses to shared buffer headers - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Do all accesses to shared buffer headers
Date
Msg-id 17415.1129176714@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Do all accesses to shared buffer headers  (Neil Conway <neilc@samurai.com>)
Responses Re: pgsql: Do all accesses to shared buffer headers  (Neil Conway <neilc@samurai.com>)
List pgsql-committers
Tree view 
Neil Conway <neilc@samurai.com> writes:
> On Wed, 2005-12-10 at 18:54 -0400, Tom Lane wrote:
>> We do however have here a New Coding Rule that's good for all parts
>> of the backend: if you are accessing a spinlock-protected data structure
>> then you should be using a volatile-qualified pointer for it.

> I think this is worth documenting more clearly

BTW, forgot to reply to this part, but: have at it.

            regards, tom lane

pgsql-committers by date:

Previous
From: momjian@svr1.postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Update trigger demo to reflect new trigger ordering.
Next
From: neilc@svr1.postgresql.org (Neil Conway)
Date:
Subject: pgsql: Add a comment describing the requirement that pointers into