Re: like pg_shmem_allocations, but fine-grained for DSM registry ?

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 16:13:04
Message-ID: A0F3D14A-D525-4B8C-AB61-8EE358C5CAD3@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 8 Jul 2025, at 11:21 PM, Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
>
> On Tue, Jul 08, 2025 at 07:17:54PM +0800, Florents Tselai wrote:
>> 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?
>
> Yeah, I'm not sure what else we can do about that without a bunch of
> refactoring work on the DSA/dshash side, and it's probably not worth the
> effort, anyway.

I agree. In that case I think v5 should be enough.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2025-07-08 16:40:28 Re: Inconsistent LSN format in pg_waldump output
Previous Message Cédric Villemain 2025-07-08 16:06:00 Re: Adding basic NUMA awareness - Preliminary feedback and outline for an extensible approach