| From: | Florents Tselai <florents(dot)tselai(at)gmail(dot)com> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: like pg_shmem_allocations, but fine-grained for DSM registry ? |
| Date: | 2025-07-08 11:17:54 |
| Message-ID: | 9200A2B4-7C24-4818-8828-22340E70AB3C@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 25 Jun 2025, at 4:33 AM, Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
>
> for DSAs and dshash tables, we probably want to use dsa_get_total_size()
> for the "size" column.
>
The thing is that dsa_get_total_size expects an already attached dsa.
I can't see how it's possible to get the actual size for the dsa and dsh case,
without attaching and then using, dsa_get_total_size on the attached dsa.
And I don't think we wanna do that.
Instead maybe we can just report NULL for the dsa and dsh cases?
Here’s a v5 that does it like that
| Attachment | Content-Type | Size |
|---|---|---|
| v5-0001-Update-pg_dsm_registry_allocations-to-include-stu.patch | application/octet-stream | 10.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2025-07-08 11:19:38 | Re: A recent message added to pg_upgade |
| Previous Message | Rahila Syed | 2025-07-08 11:06:29 | Re: Small optimization with expanding dynamic hash table |