| From: | shihao zhong <zhong950419(at)gmail(dot)com> |
|---|---|
| To: | Alexandre Felipe <o(dot)alexandre(dot)felipe(at)gmail(dot)com> |
| Cc: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: aio: worker: Free SMGR objects when idle |
| Date: | 2026-10-05 18:43:23 |
| Message-ID: | CAGRkXqRkCwNhrR-yXkJ+WKOqpy9d7J8092dOiLB7PFetzVw1Ng@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Alexandre,
> About touching LRU, I thought that the I/O worker already updated the
> LRU list every operation, does it go through a different path?
You are right, FileAccess() in fd.c moves the file to the head of its
LRU ring on every read and write, so that part costs nothing new. I
was wrong there.
I still think v3 is enough for this patch, but I will leave it to
Nazir and Andres.
Thanks,
Shihao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias van de Meent | 2026-10-05 18:45:36 | Re: Limiting WAL retained for archiving, like max_slot_wal_keep_size |
| Previous Message | Manu | 2026-10-05 18:41:50 | Re: UNDO with constant time recovery (CTR) |