From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dan Moschuk <dan(at)freebsd(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | FreeBSDers paying attention? (was Re: exit status 26) |
Date: | 2001-01-12 20:49:36 |
Message-ID: | 4556.979332576@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dan Moschuk <dan(at)freebsd(dot)org> writes:
> | > So it is getting a virtual timer from somewhere. A grep of the backend
> | > directory revealed no setitimer() occurances, so I can confirm that it
> | > isn't postmaster doing it. And if the shells environment is unlimited,
> | > which doesn't leave very many culprits left. :/
> |
> | Yes. It would be good to question my assumption that the exit code
> | is a signal --- I can't see what else it could be, but can you run
> | the backend with a breakpoint set at exit(), and get a backtrace?
> Unfortunately, after upgrading the machine to 4.2-RELEASE, I cannot reproduce
> this problem any longer. :/
> If anyone has a 4.1-RELEASE machine kicking around, I'd love to be able
> to try and track this down further.
I know we've got plenty of FreeBSD people on this list; surely someone
can lend you an account on a 4.1 machine. I changed the Subject: line
just to get the right peoples' attention ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Mercer | 2001-01-12 20:57:41 | Re: FreeBSDers paying attention? (was Re: exit status 26) |
Previous Message | Bruno Wolff III | 2001-01-12 20:45:28 | Re: Time Formats |