Hi all,

I regularly do a "cvs update" and compile and test PostgreSQL.

Recently, since about 1 week, I've had a nasty problem.

Doing an "initdb" seems to suck up all available memory and almost
kills the system, before dying itself with a SEGV.

The problem postgress process is:-

  /usr/local/pgsql/bin/postgres -boot -x -C -F -D/usr/local/pgsql/data -d 
template1
  
The system becomes VERY unresponsive when this postgres process
starts running, so difficult to attach to with gdb. 

I'm stuck for a clue as to how to debug this.

Is anyone else seeing this problem recently?

Is it just a Solaris problem?
(Solaris 2.6 on SPARCstation 5)

Is it just me? :-(

Help,

Keith.


Thu, 1 Jun 2000 21:31:17 +0100 (BST)
Keith Parks <emkxp01@mtcc.demon.co.uk>
Problems with recent CVS versions and Solaris.
Keith Parks <emkxp01@mtcc.demon.co.uk> writes:
> Recently, since about 1 week, I've had a nasty problem.
> Doing an "initdb" seems to suck up all available memory and almost
> kills the system, before dying itself with a SEGV.

Hmm --- no such problem noted here, and I've been doing lots of initdbs...

It must be somewhat platform-specific.  See if you can get a coredump
and backtrace.

			regards, tom lane

Thu, 01 Jun 2000 17:48:23 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: Problems with recent CVS versions and Solaris. 