| From: | Shawn Debnath <clocksweep(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru> |
| Subject: | Re: SLRUs in the main buffer pool, redux |
| Date: | 2023-01-20 17:00:18 |
| Message-ID: | Y8rIorfkihuzoVqG@ip-10-0-1-30.us-west-2.compute.internal |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 25, 2022 at 11:54:36AM +0300, Heikki Linnakangas wrote:
> Oh I just saw that you had a comment about that in the patch and had hacked
> around it. Anyway, calling ResourceOwnerEnlargeBuffers() might be a
> solution. Or switch to a separate "CriticalResourceOwner" that's guaranteed
> to have enough pre-allocated space, before entering the critical section.
Wanted to bump up this thread. Rishu in my team posted a patch in the other
SLRU thread [1] with the latest updates and fixes and looks like performance
numbers do not show any regression. This change is currently in the
January commitfest [2] as well. Any feedback would be appreciated!
[1]
https://www.postgresql.org/message-id/A09EAE0D-0D3F-4A34-ADE9-8AC1DCBE7D57%40amazon.com
[2] https://commitfest.postgresql.org/41/3514/
Shawn
Amazon Web Services (AWS)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-01-20 17:09:05 | Re: run pgindent on a regular basis / scripted manner |
| Previous Message | Bruce Momjian | 2023-01-20 16:42:33 | Re: run pgindent on a regular basis / scripted manner |