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