From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Justin Pasher <justinp(at)newmediagateway(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Autovacuum daemon terminated by signal 11 |
Date: | 2009-01-17 15:49:54 |
Message-ID: | 12265.1232207394@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Hmm, in retrospect this is pretty obviously buggy. I can't say that
> it's that easy for me to reproduce it though; I definitely can't make it
> crash. Maybe by sheer luck, the new TopTransactionContext pointer
> points to the same memory area that the old was stored in.
Yeah, there could be some platform dependency involved. I'm guessing
different structs that happen to fall into the same palloc size category
on one platform but not another.
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.
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
unknown_filename | text/plain | 1.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-01-17 16:35:18 | Re: MemoryContextSwitchTo (Re: [GENERAL] Autovacuum daemon terminated by signal 11) |
Previous Message | johnf | 2009-01-17 15:21:37 | Re: executing a sql script |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-01-17 15:52:49 | Re: pg_dump versus views and opclasses |
Previous Message | Brendan Jurd | 2009-01-17 15:33:26 | Re: pg_dump versus views and opclasses |