| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Justin Pasher <justinp(at)newmediagateway(dot)com> |
| Cc: | Richard Huxton <dev(at)archonet(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Autovacuum daemon terminated by signal 11 |
| Date: | 2009-01-15 18:43:29 |
| Message-ID: | 9507.1232045009@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Justin Pasher <justinp(at)newmediagateway(dot)com> writes:
> Richard Huxton wrote:
>> Segmentation fault - probably a bug or bad RAM.
> It's a relatively new machine, but that's obviously a possibility with
> any hardware. I haven't seen any other programs experiencing problems on
> the box, but the Postgres daemon is the one that is primarily utilized,
> so it's a little biased toward that.
I agree that the behavior seems a bit too specific to be a hardware
issue.
Can you get a stack trace from the crash? You might need to restart the
postmaster under "ulimit -c unlimited" to get a core dump from the
crashing autovacuum process.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-01-15 18:54:38 | Re: MD5 password issue |
| Previous Message | Alvaro Herrera | 2009-01-15 18:42:01 | Re: Autovacuum daemon terminated by signal 11 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-01-15 18:44:57 | Re: FWD: Re: Updated backslash consistency patch |
| Previous Message | Alvaro Herrera | 2009-01-15 18:42:01 | Re: Autovacuum daemon terminated by signal 11 |