Usage of ProcessConfigfile in SIGHUP_Handler

From: Lakshmi Narayana Velayudam <dev(dot)narayana(dot)v(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Usage of ProcessConfigfile in SIGHUP_Handler
Date: 2024-08-22 12:07:13
Message-ID: CAA4pTn+2pUEJ_WVF493uBqdmqUQrdSpHJm41advrTnpbtDaN7A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi pgsql hacker,

Recently I have been trying to understand why GUC changes will be visible
even though they are done in the signal handler as part of
*ProcessConfigfile* (done in some extension code). Later I have seen almost
all postgresql processes/bgworkers use signal handler to set a
variable *ConfigReloadPending
*which will later be read in main code to process guc changes but for
postmaster *ProcessConfigfile *is being called from signal handler itself
which intern has memory allocation related code (non-async safe code). Is
it safe to do this?

Regards,
Narayana

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2024-08-22 12:07:32 Re: On disable_cost
Previous Message David Rowley 2024-08-22 12:02:48 Re: Redundant Result node