Re: "could not reattach to shared memory" on buildfarm member dory - Mailing list pgsql-hackers

From Tom Lane
Subject Re: "could not reattach to shared memory" on buildfarm member dory
Date
Msg-id 31967.1524881212@sss.pgh.pa.us
Whole thread Raw
In response to Re: "could not reattach to shared memory" on buildfarm member dory  (Noah Misch <noah@leadboat.com>)
Responses Re: "could not reattach to shared memory" on buildfarm member dory  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Noah Misch <noah@leadboat.com> writes:
> On Tue, Apr 24, 2018 at 11:37:33AM +1200, Thomas Munro wrote:
>> Maybe try asking what's mapped there with VirtualQueryEx() on failure?

> +1.  An implementation of that:
> https://www.postgresql.org/message-id/20170403065106.GA2624300%40tornado.leadboat.com

Not seeing any other work happening here, I pushed a little bit of
quick-hack investigation code.  This is based on noting that
VirtualAllocEx is documented as rounding the allocation up to a page
boundary (4K), but there's nothing specific about whether or how much
CreateFileMapping or MapViewOfFileEx might round up.  The observed
failures could be explained if those guys might eat more virtual
address space for the same request size as VirtualAllocEx does.
This is a stretch, for sure, but given the lack of any other theories
we might as well check it.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Postgres, fsync, and OSs (specifically linux)
Next
From: David Rowley
Date:
Subject: Re: Remove mention in docs that foreign keys on partitioned tablesare not supported