Re: Vacuuming the operating system documentation

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Vacuuming the operating system documentation
Date: 2020-06-08 05:44:06
Message-ID: 9496eb71-beed-efd3-b562-57abd652941f@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2020-06-08 05:50:44 Re: BufFileRead() error signalling
Previous Message David Fetter 2020-06-08 04:38:33 Bump default wal_level to logical