From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
Cc: | nitrogenycs(at)web(dot)de, pgsql-hackers-win32(at)postgresql(dot)org |
Subject: | Re: initdb crash |
Date: | 2004-07-04 14:04:30 |
Message-ID: | 833.1088949870@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers-win32 |
"Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
> It *will* say signalled by code 5 when it is actually exiting with
> normal exitcode 5.
> This is because of the WIFSIGNALED() macro in port.h.
Hm. Whether those macros are wrong or not, we're still left wondering
why it would exit(5), either.
The crash is apparently coming during the first attempt to insert a row
from the postgres.bki file. That does not seem consistent with the
theory about a permissions problem; if we had no directory permissions
I'd have expected a failure at the previous "create pg_proc" step. (For
that matter, how'd we have managed to create all the subdirectories and
configuration files? The permissions theory doesn't hold water at all.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-07-04 14:09:31 | Re: initdb crash |
Previous Message | Gary Doades | 2004-07-04 13:58:37 | Re: initdb crash |