| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, 陈佳昕(步真) <buzhen(dot)cjx(at)alibaba-inc(dot)com> |
| Subject: | Re: 回复：Re: Cache relation sizes? |
| Date: | 2021-06-16 06:24:01 |
| Message-ID: | CA+hUKGJg+gqCs0dgo94L=1J9pDp5hKkotji9A05k2nhYQhF4+w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
No change yet, just posting a rebase to keep cfbot happy.
One thing I'm wondering about is whether it'd be possible, and if so,
a good idea, to make a kind of tiny reusable cache replacement
algorithm, something modern, that can be used to kill several birds
with one stone (SLRUs, this object pool, ...). Or if the interlocking
requirements make it too integrated.
| Attachment | Content-Type | Size |
|---|---|---|
| v5-0001-WIP-Track-relation-sizes-in-shared-memory.patch | text/x-patch | 35.0 KB |
| v5-0002-WIP-Provide-a-lock-free-fast-path-for-smgrnblocks.patch | text/x-patch | 6.7 KB |
| v5-0003-update-fifo-to-lru-to-sweep-a-valid-cache.patch | text/x-patch | 5.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2021-06-16 06:24:20 | Re: snapshot too old issues, first around wraparound and then more. |
| Previous Message | Amit Kapila | 2021-06-16 06:01:57 | Re: Question about StartLogicalReplication() error path |