make check hangs in alpha5

* Environment:
CentOS 5.2 on VirtualBox 3.0.6 of WindowsXP SP3

$ uname -a
Linux localhost.localdomain 2.6.18-92.1.22.el5 #1 SMP Tue Dec 16
12:03:43 EST 2008 i686 i686 i386 GNU/Linux

$ gcc -v
Target: i386-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-libgcj-multifile
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada
--enable-java-awt=gtk --disable-dssi --enable-plugin
--with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
--with-cpu=generic --host=i386-redhat-linux
Thread model: posix
gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)

* Fact:
In Alpha4, Alpha5 and some snapshots from about middle of Jan, "make
check" hangs with an error

./pg_regress --inputdir=. --dlpath=. --multibyte=SQL_ASCII
--temp-install=./tmp_check --top-builddir=../../..
--schedule=./parallel_schedule
============== creating temporary installation        ==============
============== initializing database system           ==============
============== starting postmaster                    ==============

pg_regress: postmaster did not respond within 60 seconds
Examine /home/forcia/work/postgresql/src/test/regress/log/postmaster.log
for the reason
make[2]: *** [check] Error 2
make[2]: Leaving directory `/home/forcia/work/postgresql/src/test/regress'
make[1]: *** [check] Error 2
make[1]: Leaving directory `/home/forcia/work/postgresql/src/test'
make: *** [check] Error 2

$ cat src/test/regress/log/postmaster.log
LOG:  database system was shut down at 2010-04-04 16:35:37 JST
LOG:  autovacuum launcher started
LOG:  database system is ready to accept connections
== end of log ==

Attached is another log with debug5. I run "make maintainer-clean"
every time before "make check".

$ ./configure CFLAGS= --enable-debug --enable-cassert

It seems postgres starts up successfully with aux processes but
doesn't accept neither UNIX domain socket / TCP socket. When I run
postgres from console with the same option that pg_regress forks it
accepts. This occurs only when pg_regress spawns postgres process.

* My investigation so far:
My bisect-ish (manual, actually :) research found that the failure
begins with the commit:
<Introduce two new libpq connection functions, PQconnectdbParams and>
http://git.postgresql.org/gitweb?p=postgresql.git;a=commit;h=cc6c533b43b5244cf4af58709340bb7b9af26cce

But this commit is OK:
<Fix bug in wasender's xlogid boundary handling, reported by Erik Rijkers.>
http://git.postgresql.org/gitweb?p=postgresql.git;a=commit;h=c46f3447f1efbc9fbc30ce5d5b9c65bd75e10b89

The problem isn't in libpq, since it is that the server doesn't listen
on startup as above. No /tmp/.s.PGSQL.5432, nor LISTENING entry in
netstat. And not only the target version psql but 8.4's psql cannot
connect to the database.

I cannot figure out at all what is wrong. Have any idea?

Regards,


--
Hitoshi Harada