Re: shared memory based stat collector (was: Sharing record typmods between backends)
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, Thomas Munro <thomas.munro@enterprisedb.com>, Dilip Kumar <dilipbalaut@gmail.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2017-08-14T16:36:10Z
Lists: pgsql-hackers
On 2017-08-14 12:28:39 -0400, Tom Lane wrote: > Robert Haas <robertmhaas@gmail.com> writes: > > On Mon, Aug 14, 2017 at 12:16 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > >> Just FYI, the only values being reported by buildfarm animals are > >> "posix", "sysv", and "windows". So while mmap may be a thing, > >> it's an untested thing. > > > I'm pretty sure I dev-tested it before committing anything, but, > > certainly, having ongoing BF coverage woudn't be a bad thing. > > Looking closer, the reason those are the only reported values is > that those are the only possible results from initdb's > choose_dsm_implementation(). So the real question here is whether > "mmap" should be considered to dominate "sysv" if it's available. No mmap isn't a good option - it's file backed mmap, rather than anonymous mmap. To my knowledge there's no good portable way to use anonymous mmap to share memory across processes unless established before a fork(). > If so, why isn't choose_dsm_implementation() trying it; and if not, > why are we carrying it? I think the idea was that there might be platforms that require it, but ... Greetings, Andres Freund
Commits
-
Simplify autovacuum work-item implementation
- f2f9fcb3030b 10.0 landed
- 31ae1638ce35 11.0 landed
-
Fix error handling path in autovacuum launcher
- d9a622cee162 11.0 landed
- 870da1e1546c 10.0 landed
-
Dramatically reduce System V shared memory consumption.
- b0fc0df9364d 9.3.0 cited