| 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-30 16:14:51 |
| Message-ID: | 20171030161451.leaglbczlriuocvw@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> 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.
I ended up backpatching 335f3d04e4c8.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2017-10-30 16:17:42 | Re: pow support for pgbench |
| Previous Message | David Fetter | 2017-10-30 15:06:33 | Re: Jsonb transform for pl/python |