Re: Move PinBuffer and UnpinBuffer to atomics

From: Andres Freund <andres(at)anarazel(dot)de>
To: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>,Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Dilip Kumar <dilipbalaut(at)gmail(dot)com>,Robert Haas <robertmhaas(at)gmail(dot)com>,Merlin Moncure <mmoncure(at)gmail(dot)com>,Michael Paquier <michael(dot)paquier(at)gmail(dot)com>,YUriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>,pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Move PinBuffer and UnpinBuffer to atomics
Date: 2016-04-09 19:49:29
Message-ID: 2C486F8E-0D5C-4547-86D1-FC9A1DA9A4ED@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On April 9, 2016 12:43:03 PM PDT, Andres Freund <andres(at)anarazel(dot)de> wrote:
>On 2016-04-09 22:38:31 +0300, Alexander Korotkov wrote:
>> There are results with 5364b357 reverted.
>
>Crazy that this has such a negative impact. Amit, can you reproduce
>that? Alexander, I guess for r/w workload 5364b357 is a benefit on that
>machine as well?

How sure are you about these measurements? Because there really shouldn't be clog lookups one a steady state is reached...

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2016-04-09 20:01:28 Sort push down through a nested loop, for 9.7
Previous Message Andres Freund 2016-04-09 19:43:03 Re: Move PinBuffer and UnpinBuffer to atomics