From: | Fabrice Scemama <fabrices(at)ximmo(dot)ftd(dot)fr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Vacuum problem in my system ? |
Date: | 2000-06-05 20:36:00 |
Message-ID: | 393C0F30.86E652AA@ximmo.ftd.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
No core dump could be found within the data/base/*
directories. The cron is executed by user root,
but on my system root is a PostgreSQL superuser.
Tom Lane wrote:
>
> Fabrice Scemama <fabrices(at)ximmo(dot)ftd(dot)fr> writes:
> > [ vacuum appears to be coredumping ]
>
> That's odd ... not so much that vacuum could be failing, which is
> probably a garden-variety bug; but it sounds like the postmaster is
> failing to do the system restart that it should do after one of the
> backends fails. Is there anything showing up in the postmaster log
> when this happens?
>
> As for tracking the immediate vacuum problem, the failed backend
> should have left a core dump file in the database directory
> (.../data/base/DBNAME/core). Can you get a backtrace from that
> with gdb? Something like
> gdb path/to/postgres path/to/core
> bt
> quit
> should do.
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Aaron Sethman | 2000-06-05 21:08:09 | Finding number of updated rows in pl/pgsql |
Previous Message | rocael | 2000-06-05 20:01:15 | moving DB |