Re: Posgresql 7.2b1 crashes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 1 Nov 2001, Tom Lane wrote:

> "Mr. Shannon Aldinger" <god(at)yinyang(dot)hjsoft(dot)com> writes:
> > I don't have a core file, it died overnight both times so i don't know
> > exactly but I can give you the general query it performs. By crash i mean
> > the postmaster process is gone along with it's sub-processes or threads.
>
> Postmaster dies too? Wow. If you aren't seeing a core file, perhaps
> it's because you are starting the postmaster under "ulimit -c 0".
> You need the process context to be "ulimit -c unlimited" to allow cores
> to be dropped. Might be worth running with -d 2 to enable query logging
> as well.
>
I'm not sure about the ulimit, I restarted postmaster with -d 1 a few
minutes ago, I'll check the ulimit and restart it again and hopefully it
dies with some useful info this time.

> Since you didn't use --enable-locale, it's irrelevant; AFAIK we don't
> call strcoll() unless that option's been selected. The known forms of
> the strcoll problem wouldn't cause a postmaster crash anyway, only
> backend crashes. So you've got something new. Please keep us posted.
>

I probably won't have any new info till tommorow morning EST, it died once
around 4am, the other at 5:25am so it's kinda hard to tell what made it go
belly up at this point.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iEYEARECAAYFAjvhmvkACgkQwtU6L/A4vVDjuwCdG0UhoVvE4weow0P1wPxAZuha
hioAoK9SttvMZadAyoAJxKQgFTHHWmb8
=Hjr9
-----END PGP SIGNATURE-----