Re: GetNamedLWLockTranche crashes on Windows in normal backend

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Sami Imseih <samimseih(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GetNamedLWLockTranche crashes on Windows in normal backend
Date: 2025-08-25 16:46:35
Message-ID: aKyTa-iOdAfKynI1@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 22, 2025 at 02:21:55PM -0500, Sami Imseih wrote:
> While working on [0], I observed that $SUBJECT. I encountered this issue
> while building test cases for [0], and in which GetNamedLWLockTranche is
> called outside of startup.
>
> [...]
>
> I repro'd this on a Windows machine, but one can also enable EXEC_BACKEND
> in pg_config_manual.h and call GetNamedLWLockTranche by a normal backend.
>
> I did this by injecting
> ```
> GetNamedLWLockTranche("pg_stat_statements");
> ```
> inside pgss_ExecutorEnd

If this fails, why doesn't the call in pgss_shmem_startup() also fail? Was
pg_stat_statements not loaded via shared_preload_libraries? And is the
failure a segfault or a "requested tranche is not registered" error?

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Antonin Houska 2025-08-25 16:54:12 Re: Adding REPACK [concurrently]
Previous Message Robert Treat 2025-08-25 16:36:10 Re: Adding REPACK [concurrently]