From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
---|---|
To: | "Alvaro Herrera" <alvherre(at)dcc(dot)uchile(dot)cl> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: FW: getting a crash during initdb |
Date: | 2004-04-26 17:22:05 |
Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB34101ADDD@Herge.rcsinc.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> > The AV is in postgres.exe following the first SQL call in
> > setup_depend(). The problem is not in initdb (it hasn't changed)
but
> > something in the backend. Changing the SQL statement made no
> > difference: I'd venture a guess that postgres.exe crashes when *any*
> > statement is sent to it. About 20 files have changed since my last
> > initdb; I have a list. Forced initdb + initdb crash = nasty bug,
even
> > if it's just the cvs version (specific only to windows?).
>
> I've initdb'd more than twenty times with CVS tip code, so it would
seem
> to be Windows-specific.
Thought as much. I posted to the win32 list but it hasn't shown up yet.
> Are you sure you're using a clean build and a really current checkout?
Yes, 100%.
Merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2004-04-26 17:25:41 | Re: [HACKERS] What can we learn from MySQL? |
Previous Message | Shachar Shemesh | 2004-04-26 17:20:15 | Re: Do we prefer software that works or software |