Re: less expensive pg_buffercache on big shmem - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: less expensive pg_buffercache on big shmem
Date
Msg-id CAM3SWZQkmhuB2fiEy2mmB0yVGOyqP8AuOMkGrJgvca8dVkG8Ew@mail.gmail.com
Whole thread Raw
In response to Re: less expensive pg_buffercache on big shmem  (andres@anarazel.de (Andres Freund))
List pgsql-hackers
On Thu, Sep 1, 2016 at 8:19 PM, Andres Freund <andres@anarazel.de> wrote:
> On 2016-09-02 08:31:42 +0530, Robert Haas wrote:
>> I wonder whether we ought to just switch from the consistent method to
>> the semiconsistent method and call it good.
>
> +1. I think, before long, we're going to have to switch away from having
> locks & partitions in the first place. So I don't see a problem relaxing
> this. It's not like that consistency really buys you anything...  I'd
> even consider not using any locks.

Right. ISTM that the consistency guarantee was added on the off chance
that it mattered, without actually being justified. I would like to be
able to run pg_buffercache in production from time to time.


-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: andres@anarazel.de (Andres Freund)
Date:
Subject: Re: less expensive pg_buffercache on big shmem
Next
From: Amit Kapila
Date:
Subject: Re: Hash Indexes