Re: Extension Enhancement: Buffer Invalidation in pg_buffercache
От | Maksim Milyutin |
---|---|
Тема | Re: Extension Enhancement: Buffer Invalidation in pg_buffercache |
Дата | |
Msg-id | fbdb6b7a-cab4-4002-8266-955d85d70171@gmail.com обсуждение исходный текст |
Ответ на | Re: Extension Enhancement: Buffer Invalidation in pg_buffercache (Thomas Munro <thomas.munro@gmail.com>) |
Список | pgsql-hackers |
On 29.04.2024 23:59, Thomas Munro wrote:
On Tue, Apr 30, 2024 at 7:17 AM Thomas Munro <thomas.munro@gmail.com> wrote:On Tue, Apr 30, 2024 at 6:47 AM Maksim Milyutin <milyutinma@gmail.com> wrote:Should not we call at the end the StrategyFreeBuffer() function to add target buffer to freelist and not miss it after invalidation?Please take a look at this issue, current implementation of EvictUnpinnedBuffer() IMO is erroneous - evicted buffers are lost permanently and will not be reused againI don't think that's true: it is not lost permanently, it'll be found by the regular clock hand. Perhaps it should be put on the freelist so it can be found again quickly, but I'm not sure that's a bug, is it?
Yeah, you are right. Thanks for clarification.
CLOCK algorithm will reuse it eventually but being of evicted cleared buffer in freelist might greatly restrict the time of buffer allocation when all others buffers were in use.
-- Best regards, Maksim Milyutin
В списке pgsql-hackers по дате отправления: