Re: NULL pointer dereference in syslogger with load_libraries() and -DEXEC_BACKEND at startup

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Anton Voloshin <a(dot)voloshin(at)postgrespro(dot)ru>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Euler Taveira <euler(at)eulerto(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: NULL pointer dereference in syslogger with load_libraries() and -DEXEC_BACKEND at startup
Date: 2026-07-15 16:14:30
Message-ID: alew9Lk3BXiGZsm7@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2026-Jul-15, Anton Voloshin wrote:

> On 08/06/2026 21:03, Álvaro Herrera wrote:
>
> > --- a/src/include/postmaster/syslogger.h
> > +++ b/src/include/postmaster/syslogger.h
> > @@ -85,6 +85,7 @@ extern PGDLLIMPORT int syslogPipe[2];
> > extern PGDLLIMPORT HANDLE syslogPipe[2];
> > #endif
> >
> > +extern bool syslogger_setup_done;
>
> Shouldn't this be extern *PGDLLIMPORT* bool ... ?

Hmm, does that export the symbol so that third-party code can get at it?
I'm not sure it makes sense to do it for this one symbol, which should
be internal business between syslogger and elog only.

Did you hit a problem with it? If so, what was it?

Michael, looking at
https://github.com/michaelpq/pg_plugins/blob/main/jsonlog/jsonlog.c
do you see an issue with this variable?

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"La espina, desde que nace, ya pincha" (Proverbio africano)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2026-07-15 16:27:19 Re: Unexpected changes of CurrentResourceOwner and CurrentMemoryContext
Previous Message Tom Lane 2026-07-15 15:53:40 Re: [PATCH] The heap_getsysattr function deletes unused parameters