Re: Weird PostgreSQL crashes on FC2/FC3 64-bit

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: William Yu <wyu(at)talisys(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: Weird PostgreSQL crashes on FC2/FC3 64-bit
Date: 2005-02-02 09:31:20
Message-ID: 20050202093120.GA18657@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Feb 01, 2005 at 10:32:15PM -0800, William Yu wrote:
> Tom Lane wrote:
> >William Yu <wyu(at)talisys(dot)com> writes:
> >
> >>Doing a ps -ef | grep postgres, I will see something like:
> >
> >
> >>root 17034 1 0 21:41 ? 00:00:00 gdb -q -x /dev/stdin
> >>postgres 9131
> >>postgres 9131 2712 0 20:31 ? 00:00:00 postgres: postgres
> >>netdata [local] VACUUM
> >
> >
> >So where did the gdb come from?
>
> To be honest, I do not know. I see the parent process is 1 so something
> in the FCx kernel is triggering it. I just don't know where the logs for
> something like this would be.

Parent process 1 just means that it's either spawned by init or it's
real parent process has died. I wouldn't put any stock in it. Try using
"ps aux" to get the process state. Chances are it's in T (trace) state.
You can try to kill -CONT it. Maybe strace it.
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message mike 2005-02-02 09:59:30 When is a blank not a null or ''
Previous Message Sim Zacks 2005-02-02 09:16:56 modifying views