-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 1 Nov 2001, Tom Lane wrote:
> "Mr. Shannon Aldinger" <god@yinyang.hjsoft.com> writes:
> > I've had two overnight crashes with postgresql-7.2b1. Neither logged any
> > useful info in the logfile created by pg_ctl, syslog or messages.
>
> Please define "crash". If it was a coredump, how about a stack
> backtrace? Can you determine what query it was executing?
>
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.
It runs several hundred of these queries per day:
select error from accessdb where lower(email)=lower('%s') limit 1;
%s is usually replaced with an email address, domain name or ip address.
> While I'd like to help you, you have not provided one single bit of
> information that could possibly be used to identify the problem ...
>
Sorry, but i've been unable to gather all that much about the problem.
I started postmaster with -B 512 -N 64 -i, I'm going to try to up the
debugging level and see if it gives anymore incite into why it crashed.
> > glibc-2.2.x.
>
> ... except perhaps that. If you compiled with --enable-locale, an
> update to glibc 2.2.3 is strongly advised. There's a nasty bug in
> strcoll() in 2.2.x.
>
I think i'm running 2.2.3, but i'm not 100% sure.
from config.status:
./configure --enable-multibyte --with-maxbackends=128 --with-openssl
- --enable-odbc --with-CXX --with-gnu-ld --enable-syslog
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iEYEARECAAYFAjvhkZQACgkQwtU6L/A4vVDD+gCfeOlPaEgRtdtRtjy6Ku7l2/jh
M/0An2OT5vNFrfx2vc5FjpzccAiBi2sg
=Ry99
-----END PGP SIGNATURE-----
