| 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: | 20070429162202.GG18593@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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 http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-04-29 16:25:52 | Re: strange buildfarm failures |
| Previous Message | Tom Lane | 2007-04-29 16:21:16 | Re: Reducing stats collection overhead |