Horton

Re: add function for creating/attaching hash table in DSM registry

Nathan Bossart <nathandbossart@gmail.com>

View thread View on postgr.es
From: Nathan Bossart <nathandbossart@gmail.com>
To: Florents Tselai <florents.tselai@gmail.com>
Cc: Sami Imseih <samimseih@gmail.com>, Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>, pgsql-hackers@postgresql.org
Date: 2025-06-10T17:25:49Z
Lists: pgsql-hackers

Attachments

On Tue, Jun 10, 2025 at 07:47:02PM +0300, Florents Tselai wrote:
> Love this new API.

Thanks!

> a minor typo here 
> + * current backend.  This function gurantees that only one backend

Fixed.

> Since you made the first step towards decoupling DSMR_NAME_LEN from NAMEDATALEN;
> is it worth considering increasing this to 128 maybe?
> 
> I´ve used DSMR extensively for namespacing keys etc, and I´ve come close to 50-60 chars at times.
> 
> I´m not too fixed on that though.

Seems fine to me.

-- 
nathan

Commits

  1. Fix cross-version upgrade test breakage from commit fe07100e82.

  2. Add GetNamedDSA() and GetNamedDSHash().

  3. Remove dynamic_shared_memory_type=none

  4. Introduce dynamic shared memory areas.

  5. Relax the requirement that all lwlocks be stored in a single array.