Re: Vacuuming the operating system documentation - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Vacuuming the operating system documentation
Date
Msg-id 9496eb71-beed-efd3-b562-57abd652941f@2ndquadrant.com
Whole thread Raw
In response to Re: Vacuuming the operating system documentation  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Vacuuming the operating system documentation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2020-06-07 17:00, Tom Lane wrote:
> Relevant to the current discussion: this creates a possible positive
> reason for setting dynamic_shared_memory_type to "sysv", namely if it's
> the best available way to get around RemoveIPC in a particular situation.
> Should we document that?

It sounds like both shared_memory_type and dynamic_shared_memory_type 
ought to default to "sysv" on Linux.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Bump default wal_level to logical
Next
From: Thomas Munro
Date:
Subject: Re: BufFileRead() error signalling