Re: Some shared memory chunks are allocated even if related processes won't start - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Some shared memory chunks are allocated even if related processes won't start
Date
Msg-id 202403040809.ovvbwsmerzer@alvherre.pgsql
Whole thread Raw
In response to Some shared memory chunks are allocated even if related processes won't start  ("Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>)
Responses RE: Some shared memory chunks are allocated even if related processes won't start
List pgsql-hackers
On 2024-Mar-04, Hayato Kuroda (Fujitsu) wrote:

> Dear hackers,
> 
> While reading codes, I found that ApplyLauncherShmemInit() and
> AutoVacuumShmemInit() are always called even if they would not be
> launched.

Note that there are situations where the autovacuum launcher is started
even though autovacuum is nominally turned off, and I suspect your
proposal would break that.  IIRC this occurs when the Xid or multixact
counters cross the max_freeze_age threshold.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"Porque Kim no hacía nada, pero, eso sí,
con extraordinario éxito" ("Kim", Kipling)



pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: Fix log_line_prefix to display the transaction id (%x) for statements not in a transaction block
Next
From: Andres Freund
Date:
Subject: Re: Avoid stack frame setup in performance critical routines using tail calls