From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: SIGSEGV in BRIN autosummarize |
Date: | 2017-10-24 10:39:12 |
Message-ID: | 20171024103912.nux6i2oqmpxwi34x@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> Before pushing, I'll give a look to the regular autovacuum path to see
> if it needs a similar fix.
Reading that one, my conclusion is that it doesn't have the same problem
because the strings are allocated in AutovacuumMemCxt which is not reset
by error recovery. This gave me the idea to use that context instead of
TopTransactionContext to store the strings in workitem processing also.
The patch I propose now is attached.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
v2-0001-Fix-autovacuum-work-items.patch | text/plain | 2.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2017-10-24 10:39:54 | Current int & float overflow checking is slow. |
Previous Message | Thomas Munro | 2017-10-24 09:10:53 | Re: Parallel Hash take II |