From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <rhaas(at)postgresql(dot)org> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Get rid of the dynamic shared memory state file. |
Date: | 2014-04-08 20:20:08 |
Message-ID: | 26839.1396988408@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Robert Haas <rhaas(at)postgresql(dot)org> writes:
> Get rid of the dynamic shared memory state file.
The Windows buildfarm critters don't seem to like this patch.
narwhal for example:
creating directory C:/msys/1.0/local/pgbuildfarm/buildroot/HEAD/pgsql.3944/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 C:/msys/1.0/local/pgbuildfarm/buildroot/HEAD/pgsql.3944/src/test/regress/./tmp_check/data/base/1 ... LOG: dynamic shared memory control segment is corrupt
child process was terminated by exception 0xC0000005
baiji and bowerbird also crashed in initdb, though without the message
about "dynamic shared memory control segment is corrupt". Presumably
it's the same bug though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2014-04-08 20:22:29 | Re: pgsql: Get rid of the dynamic shared memory state file. |
Previous Message | Robert Haas | 2014-04-08 20:17:46 | Re: pgsql: Get rid of the dynamic shared memory state file. |