Re: [HACKERS] Clock with Adaptive Replacement - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: [HACKERS] Clock with Adaptive Replacement
Date
Msg-id 2E09D995-9294-4A21-989B-34B75F66938E@yandex-team.ru
Whole thread Raw
In response to Re: [HACKERS] Clock with Adaptive Replacement  (Юрий Соколов <funny.falcon@gmail.com>)
Responses Re: [HACKERS] Clock with Adaptive Replacement  (Юрий Соколов <funny.falcon@gmail.com>)
Re: [HACKERS] Clock with Adaptive Replacement  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers

> 24 апр. 2018 г., в 11:31, Юрий Соколов <funny.falcon@gmail.com> написал(а):
>
> Before implementing algorithms within PostgreSQL it will be great to test them outside with real traces.
>
> I think, there should be mechamism to collect traces from real-world postgresql instalations: every read and write
access.It should be extremely eficient to be enabled in real world. Something like circular buffer in shared memory,
andseparate worker to dump it to disk. 
> Instead of full block address, 64bit hash could be used. Even 63bit + 1bit to designate read/write access.
Yes, this is good idea to track pattern of blocks usage.
But, I think that cost of development of real page eviction strategy itself is neglectable small compared to
infrastructurechanges needed by any non-CS5 strategy. 

Best regards, Andrey Borodin.

pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: Expression errors with "FOR UPDATE" and postgres_fdw with partitionwise join enabled.
Next
From: Merlin Moncure
Date:
Subject: Re: Built-in connection pooling