Cygwin PostgreSQL Regression Test Problems

Over the last few days, I ran the regression tests for 7.1 Beta 3 much more
than I have in the past for 7.0.2 and 7.0.3. Unfortunately, I experienced
the following problems:

1. Until I did a cvs update last night (1/14/2001), the regression tests
were failing on 1/12 and 1/13. Did anyone do a cvs commit that would
fix backend children from stackdump-ing on Cygwin? I hope so.

Here are some interesting snippets:

--- pg_regress output ---
..
parallel group (7 tests): create_aggregate create_operator inherit triggers constraints create_misc create_index
constraints ... FAILED
triggers ... FAILED
create_misc ... FAILED
create_aggregate ... ok
..
--- pg_regress output ---

--- postmaster output ---
NOTICE: Message from PostgreSQL backend:
The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am going to terminate your database system connection and exit.
Please reconnect to the database system and repeat your query.
..
ERROR: Relation 'temptest' does not exist
0 [main] postmaster 2640 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
479 [main] postmaster 2640 stackdump: Dumping stack trace to postmaster.exe.stackdump
Server process (pid 2640) exited with status 139 at Sat Jan 13 21:28:36 2001
Terminating any active server processes...
Server processes were terminated at Sat Jan 13 21:28:36 2001
Reinitializing shared memory and semaphores
IpcMemoryDetach: shmdt(0x120b0000) failed: Invalid argument
..
--- postmaster output ---

2. I am unable to successfully run the regression tests on a NT 4.0 SP5
machine with only 64 MB of physical memory and about 175 MB of swap space.
Other than lacking RAM and swap space, this machine is the "same" as other
NT/2000 machines which can successfully run the regression tests.

The tests usually hang during the "parallel group (18 tests)" test
right after numerology. By "hang," I mean that the original postmaster
is still running, but there are no postmaster children, and there are
some number of psql processes hanging around. Using NT's TaskManager,
I can see that the machine is running out of memory. I have even seen
the "Windows is running low on virtual memory" dialog a few times.
Should I expect this behavior from such a lame machine?

3. Once (or twice), I noticed that the plpgsql test failed.
Unfortunately, I didn't capture the precise output but I think that
postmaster was complaining about being unable to

mv <somepath>/pg_internal.init.<somepid> <somepath>/pg_internal.init

due to a permissions problem. Sorry, for being vague...

Thanks,
Jason

--
Jason Tishler
Director, Software Engineering Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corp. Fax: +1 (732) 264-8798
82 Bethany Road, Suite 7 Email: Jason(dot)Tishler(at)dothill(dot)com
Hazlet, NJ 07730 USA WWW: http://www.dothill.com