Re: [HACKERS] SIGSEGV in BRIN autosummarize - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [HACKERS] SIGSEGV in BRIN autosummarize
Date
Msg-id 20171024103912.nux6i2oqmpxwi34x@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] SIGSEGV in BRIN autosummarize  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: [HACKERS] SIGSEGV in BRIN autosummarize
List 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

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: [HACKERS] Parallel Hash take II
Next
From: Andres Freund
Date:
Subject: [HACKERS] Current int & float overflow checking is slow.