Re: pgsql: Move cancel key generation to after forking the backend

2024-07-29 Thread Heikki Linnakangas
On 29/07/2024 17:30, Heikki Linnakangas wrote: On 29/07/2024 16:25, Heikki Linnakangas wrote: On 29/07/2024 16:23, Daniel Gustafsson wrote: On 29 Jul 2024, at 15:18, Heikki Linnakangas wrote: Move cancel key generation to after forking the backend longfin seems a tad sad about this one: pr

Re: pgsql: Move cancel key generation to after forking the backend

2024-07-29 Thread Heikki Linnakangas
On 29/07/2024 16:25, Heikki Linnakangas wrote: On 29/07/2024 16:23, Daniel Gustafsson wrote: On 29 Jul 2024, at 15:18, Heikki Linnakangas wrote: Move cancel key generation to after forking the backend longfin seems a tad sad about this one: procsignal.c:87:3: error: redefinition of typedef

Re: pgsql: Move cancel key generation to after forking the backend

2024-07-29 Thread Heikki Linnakangas
On 29/07/2024 16:23, Daniel Gustafsson wrote: On 29 Jul 2024, at 15:18, Heikki Linnakangas wrote: Move cancel key generation to after forking the backend longfin seems a tad sad about this one: procsignal.c:87:3: error: redefinition of typedef 'ProcSignalHeader' is a C11 feature [-Werror,-W

Re: pgsql: Move cancel key generation to after forking the backend

2024-07-29 Thread Daniel Gustafsson
> On 29 Jul 2024, at 15:18, Heikki Linnakangas > wrote: > > Move cancel key generation to after forking the backend longfin seems a tad sad about this one: procsignal.c:87:3: error: redefinition of typedef 'ProcSignalHeader' is a C11 feature [-Werror,-Wtypedef-redefinition] } ProcSignalHeader

pgsql: Move cancel key generation to after forking the backend

2024-07-29 Thread Heikki Linnakangas
Move cancel key generation to after forking the backend Move responsibility of generating the cancel key to the backend process. The cancel key is now generated after forking, and the backend advertises it in the ProcSignal array. When a cancel request arrives, the backend handling it scans the Pr