Re: BUG #4267: initdb fails - Mailing list pgsql-bugs

From Dave Page
Subject Re: BUG #4267: initdb fails
Date
Msg-id 937d27e10806270315i2584157bycb3ced0fe5f88fa8@mail.gmail.com
Whole thread Raw
In response to Re: BUG #4267: initdb fails  (Craig Ringer <craig@postnewspapers.com.au>)
Responses Re: BUG #4267: initdb fails
List pgsql-bugs
On Fri, Jun 27, 2008 at 11:08 AM, Craig Ringer
<craig@postnewspapers.com.au> wrote:
>> Hmm, interesting. Now I just need to figure out why...
>
> Process Monitor might come in handy here. If Vadim was to use it to record a
> trace of a successful initdb and of a failed one, you'd have a bit more
> information about what is actually happening to work with.

Yeah - unfortunately though recent experience with similar
hard-to-find bugs have not normally shown up in PM. They've been much
more subtle, usually requiring much poking around in Process Explorer
which is difficult to do via email.

If you can provide a Process Monitor trace of the failed initdb, it
would be useful to take a look Vadim - even if it just eliminates the
obvious problems.

http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx


--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: Craig Ringer
Date:
Subject: Re: BUG #4267: initdb fails
Next
From: Vadim Karacharsky
Date:
Subject: Re: BUG #4267: initdb fails