Re: reviewing the "Reduce sinval synchronization overhead" patch / b4fbe392f8ff6ff1a66b488eb7197eef9e1770a4 - Mailing list pgsql-hackers

From Nils Goroll
Subject Re: reviewing the "Reduce sinval synchronization overhead" patch / b4fbe392f8ff6ff1a66b488eb7197eef9e1770a4
Date
Msg-id 504D9ADC.8070809@schokola.de
Whole thread Raw
In response to Re: reviewing the "Reduce sinval synchronization overhead" patch / b4fbe392f8ff6ff1a66b488eb7197eef9e1770a4  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
This is really late, but ...

On 08/21/12 11:20 PM, Robert Haas wrote:
> Our sinval synchronization mechanism has a somewhat weird design that
> makes this OK.

... I don't want to miss the change to thank you, Robert, for the detailed 
explanation. I have backported b4fbe392f8ff6ff1a66b488eb7197eef9e1770a4 to 9.1.3 
and it is working well in production for ~2 weeks, but I must admit that I had 
put in the unnecessary read barrier into SIGetDataEntries just to be on the safe 
side. I will take it out for the next builds.

Thanks, Nils




pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Proof of concept: standalone backend with full FE/BE protocol
Next
From: Kohei KaiGai
Date:
Subject: Re: ALTER command reworks