| From: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
|---|---|
| To: | Aidar Imamov <a(dot)imamov(at)postgrespro(dot)ru> |
| Cc: | Joseph Koshakow <koshy44(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add pg_buffercache_evict_all() and pg_buffercache_mark_dirty[_all]() functions |
| Date: | 2025-03-24 12:40:05 |
| Message-ID: | CAN55FZ1zidYeath3sk9zxW1wbRKmODfZH4stRSveNwO9hE9qYQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Sun, 23 Mar 2025 at 22:16, Aidar Imamov <a(dot)imamov(at)postgrespro(dot)ru> wrote:
>
> I agree with most of what Joseph said. However, I would like to add some
> comments.
>
> At the moment, the "flushed" flag essentially indicates whether the
> buffer
> was dirty at the time of eviction and it does not guarantee that it has
> been
> written to disk.
I think flushed means 'passing the buffer contents to the kernel' in
the Postgres context (as it is explained in the FlushBuffer()). We
know that flush has happened, we just do not know if the buffer is
flushed by us or someone else.
--
Regards,
Nazir Bilal Yavuz
Microsoft
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2025-03-24 12:42:29 | Re: Allow default \watch interval in psql to be configured |
| Previous Message | Nazir Bilal Yavuz | 2025-03-24 12:39:33 | Re: Add pg_buffercache_evict_all() and pg_buffercache_mark_dirty[_all]() functions |