Skip site navigation (1) Skip section navigation (2)

Re: strange buildfarm failures

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: strange buildfarm failures
Date: 2007-04-29 16:22:02
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Stefan Kaltenbrunner wrote:

> well - i now have a core file but it does not seem to be much worth
> except to prove that autovacuum seems to be the culprit:
> Core was generated by `postgres: autovacuum worker process
>                              '.
> Program terminated with signal 6, Aborted.
> [...]
> #0  0x00000ed9 in ?? ()
> warning: GDB can't find the start of the function at 0xed9.

Interesting.  Notice how it doesn't have the database name in the ps
display.  This means it must have crashed between the initial
init_ps_display and the set_ps_display call just before starting to
vacuum.  So the bug is probably in the startup code; probably the code
dealing with the PGPROC which is the newest and weirder stuff.

Alvaro Herrera                      
The PostgreSQL Company - Command Prompt, Inc.

In response to


pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2007-04-29 16:25:52
Subject: Re: strange buildfarm failures
Previous:From: Tom LaneDate: 2007-04-29 16:21:16
Subject: Re: Reducing stats collection overhead

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group