From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Justin Pasher" <justinp(at)newmediagateway(dot)com> |
Cc: | "'Alvaro Herrera'" <alvherre(at)commandprompt(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Autovacuum daemon terminated by signal 11 |
Date: | 2009-01-18 06:15:42 |
Message-ID: | 23774.1232259342@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:
>> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>> Anyway, it happens consistently on my HP box. I find that your proposed
>> patch fixes it, but makes the "normal" path crash :-( --- the loop in
>> do_autovacuum has to be executed in AutovacMemCxt, because it creates an
>> Oid List that gets passed to vacuum() and had better not be in a
>> transaction-lifetime context. The attached modified patch works for me.
> I tried both Alvaro's patch and your patch, and I actually got the same
> results from both.
Alvaro's patch would most likely not crash in a non-assert-enabled
build, since the list wouldn't be physically damaged when the containing
context got freed. But obviously that's a risky thing ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | searchelite | 2009-01-18 06:40:09 | Re: auto insert data every one minute |
Previous Message | Justin Pasher | 2009-01-17 21:41:47 | Re: Autovacuum daemon terminated by signal 11 |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-01-18 06:24:47 | Re: Statement-level triggers and inheritance |
Previous Message | Tom Lane | 2009-01-18 06:08:52 | Re: VARSIZE - why omit VARLEN? |