| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jan Wieck <jan(at)wi3ck(dot)info>, Gregory Smith <gregsmithpgsql(at)gmail(dot)com>, John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Subject: | Re: The Free Space Map: Problems and Opportunities |
| Date: | 2021-09-07 02:08:24 |
| Message-ID: | CA+hUKG+Wo0RiAaXyPvu2jhk7ENhbx4LmzsX7g0dkuPXSbhUsxg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 26, 2021 at 5:59 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Andres has been working -- I think for years now -- on replacing the
> buffer mapping table with a radix tree of some kind. That strikes me
> as very similar to what you're doing here. The per-relation data can
> then include not only the kind of stuff you're talking about but very
> fundamental things like how long it is and where its buffers are in
> the buffer pool. Hopefully we don't end up with dueling patches.
FTR I have a patch in development that adds a demand-paged (though
Anastasia recently suggested reconsidering that) per-SMGR relation
shmem object pool that initially tracks precisely "how long it is",
but I hope it would provide a hook to hang many other things on in
future that need coordination at the relation level, such as
synchronized scan position, and I hope, radix-based buffer mappings.
Could be relevant? https://commitfest.postgresql.org/34/2933/ (I'll
rebase it soon).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Nancarrow | 2021-09-07 02:11:22 | Re: Added schema level support for publication. |
| Previous Message | Thomas Munro | 2021-09-07 01:40:51 | Re: Atomic rename feature for Windows. |