Re: reviewing the "Reduce sinval synchronization overhead" patch / b4fbe392f8ff6ff1a66b488eb7197eef9e1770a4

From: Nils Goroll <slink(at)schokola(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: reviewing the "Reduce sinval synchronization overhead" patch / b4fbe392f8ff6ff1a66b488eb7197eef9e1770a4
Date: 2012-09-10 07:46:36
Message-ID: 504D9ADC.8070809@schokola.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kohei KaiGai 2012-09-10 11:08:32 Re: ALTER command reworks
Previous Message Etsuro Fujita 2012-09-10 03:29:20 Re: Minor document updates