Re: Something fishy happening on frogmouth - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Something fishy happening on frogmouth
Date
Msg-id CAA4eK1JsaHbR-aZWmVS8mouMWBRPMMdiVaBOk2===CBsqghJAA@mail.gmail.com
Whole thread Raw
In response to Something fishy happening on frogmouth  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Something fishy happening on frogmouth  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, Oct 30, 2013 at 12:42 AM, Tom Lane <tgl@sss.pgh.pa.us> 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:
couldnot open shared memory segment "Global/PostgreSQL.851401618": Not enough space 
> child process exited with exit code 1

In windows implementation of dynamic shared memory, Size calculation
for creating dynamic shared memory is assuming that requested size for
creation of dynamic shared memory segment is uint64, which is changed
by commit d2aecae, so we need to change that calculation as well.
Please find the attached patch to fix this problem.

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: Abhijit Menon-Sen
Date:
Subject: Re: [PATCH] Use MAP_HUGETLB where supported (v3)
Next
From: Sergey Konoplev
Date:
Subject: Re: [PATCH] Use MAP_HUGETLB where supported (v3)