Re: less expensive pg_buffercache on big shmem
| От | Mark Kirkwood |
|---|---|
| Тема | Re: less expensive pg_buffercache on big shmem |
| Дата | |
| Msg-id | 5303e382-815d-6843-12eb-363877451fc5@catalyst.net.nz обсуждение исходный текст |
| Ответ на | Re: less expensive pg_buffercache on big shmem (andres@anarazel.de (Andres Freund)) |
| Список | pgsql-hackers |
On 02/09/16 15:19, Andres Freund 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. > +1 as well. When I wrote the original module I copied the design of the pg_locks view - as it was safe and consistent. Now it is clear that the ability to look at (semi-consistent) contents of the buffer cache is more important than having a theoretically correct point in time snapshot. Go for it :-) regards Mark
В списке pgsql-hackers по дате отправления: