From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: SIGSEGV in BRIN autosummarize |
Date: | 2017-10-17 12:29:22 |
Message-ID: | 20171017122922.GC13880@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 17, 2017 at 12:59:16PM +0200, Alvaro Herrera wrote:
> Anyway, can give this patch a try?
I've only compiled postgres once before and this is a production environment
(althought nothing so important that the crashes are a serious concern either).
Is it reasonable to wget the postgres tarball, apply the patch, and run the
compiled postgres binary from the source tree, without running make install or
similar ? Otherwise, would it be good enough to copy the postgres binary to
/usr/pgsql-10/bin (and reinstall the binary package later) ?
Thanks,
Justin
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2017-10-17 12:49:24 | Re: SIGSEGV in BRIN autosummarize |
Previous Message | Thomas Munro | 2017-10-17 11:27:05 | A GUC to prevent leader processes from running subplans? |