Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VbFGd-0003WD-K3 for pgsql-hackers@arkaria.postgresql.org; Tue, 29 Oct 2013 19:47:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VbFGc-0006Oi-Vi for pgsql-hackers@arkaria.postgresql.org; Tue, 29 Oct 2013 19:47:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VbFGb-0006OW-7s for pgsql-hackers@postgreSQL.org; Tue, 29 Oct 2013 19:47:53 +0000 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VbFGY-0000d3-9r for pgsql-hackers@postgreSQL.org; Tue, 29 Oct 2013 19:47:52 +0000 Received: from mfilter12-d.gandi.net (mfilter12-d.gandi.net [217.70.178.129]) by relay3-d.mail.gandi.net (Postfix) with ESMTP id BAD67A80D2; Tue, 29 Oct 2013 20:47:47 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mfilter12-d.gandi.net Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by mfilter12-d.gandi.net (mfilter12-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id sjv8OQFOXfWM; Tue, 29 Oct 2013 20:47:46 +0100 (CET) X-Originating-IP: 98.27.58.255 Received: from [192.168.10.146] (cpe-098-027-058-255.nc.res.rr.com [98.27.58.255]) (Authenticated sender: adsend@dunslane.net) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 802D2A80DF; Tue, 29 Oct 2013 20:47:45 +0100 (CET) Message-ID: <527010DF.2030905@dunslane.net> Date: Tue, 29 Oct 2013 15:47:43 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: Tom Lane CC: Robert Haas , pgsql-hackers@postgreSQL.org Subject: Re: Something fishy happening on frogmouth References: <6557.1383073940@sss.pgh.pa.us> In-Reply-To: <6557.1383073940@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 10/29/2013 03:12 PM, Tom Lane wrote: > The last two buildfarm runs on frogmouth have failed in initdb, > like this: > > creating directory d:/mingw-bf/root/HEAD/pgsql.2492/src/test/regress/./tmp_check/data ... ok > creating subdirectories ... ok > selecting default max_connections ... 100 > selecting default shared_buffers ... 128MB > selecting dynamic shared memory implementation ... windows > creating configuration files ... ok > creating template1 database in d:/mingw-bf/root/HEAD/pgsql.2492/src/test/regress/./tmp_check/data/base/1 ... FATAL: could not open shared memory segment "Global/PostgreSQL.851401618": Not enough space > child process exited with exit code 1 > > It shouldn't be failing like that, considering that we just finished > probing for acceptable max_connections and shared_buffers without hitting > any apparent limit. I suppose it's possible that the final shm segment > size is a bit larger than what was tested at the shared_buffer step, > but that doesn't seem very likely to be the explanation. What seems > considerably more probable is that the probe for a shared memory > implementation is screwing up the system state somehow. It may not be > unrelated that this machine was happy before commit d2aecae went in. > > I'll try a run with that reverted just to see if that's it. This is a 32 bit compiler on a 32 bit (virtual) machine, so the change to Size is definitely more than cosmetic here. cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers