> I have no idea what caused the pg_depend stuff to crash.

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'll check why the rmdir command is not working as expected.

Merlin


Mon, 26 Apr 2004 11:37:37 -0400
"Merlin Moncure" <merlin.moncure@rcsonline.com>
Re: FW: getting a crash during initdb
On Mon, Apr 26, 2004 at 11:37:37AM -0400, Merlin Moncure wrote:
> > I have no idea what caused the pg_depend stuff to crash.
> 
> 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.

Are you sure you're using a clean build and a really current checkout?

-- 
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"El miedo atento y previsor es la madre de la seguridad" (E. Burke)

Mon, 26 Apr 2004 13:02:38 -0400
Alvaro Herrera <alvherre@dcc.uchile.cl>
Re: FW: getting a crash during initdb
Merlin Moncure wrote:
> > I have no idea what caused the pg_depend stuff to crash.
> 
> 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'll check why the rmdir command is not working as expected.

I just poked around and couldn't figure out the cause.  Initdb should
either remove the directory if it created it, or remove everything _in_
the directory if the directory already existed.  I tried the rmdir/del
/s /q commands in a CMD window and it worked fine.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

Mon, 26 Apr 2004 13:25:56 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: FW: getting a crash during initdb