From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Justin Pryzby <pryzby@telsasoft.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: pgsql-hackers@postgresql.org
Subject: Re: SIGSEGV in BRIN autosummarize
Date: Tue, 17 Oct 2017 14:59:32 +0200
Message-ID: <8656d7ab-84f7-dc0f-0c01-5fda13e447d5@2ndquadrant.com> (raw)
In-Reply-To: <20171017122922.GC13880@telsasoft.com>
References: <20171014224220.GB22678@telsasoft.com>
<20171017105916.3rvmznxnuphn3uph@alvherre.pgsql>
<20171017122922.GC13880@telsasoft.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 10/17/2017 02:29 PM, Justin Pryzby wrote:
> 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) ?
>
You don't have to install the binaries to the same location, i.e. you
can keep both the current and modified binaries.
./configure --prefix=/path/to/alternative/binaries --enable-debug
CFLAGS="..."
To get the same compilation options you can run pg_config, look for
CONFIGURE line and then just modify add --prefix option.
And after `make install` you can add it to $PATH and start the server
using those binaries.
$ export PATH=/path/to/alternative/binaries/bin:$PATH
$ which pg_ctl
$ pg_ctl -D $DATADIR stop
$ pg_ctl -D $DATADIR start
regards
--
Tomas Vondra http://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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tomas.vondra@2ndquadrant.com, pryzby@telsasoft.com, alvherre@alvh.no-ip.org
Subject: Re: SIGSEGV in BRIN autosummarize
In-Reply-To: <8656d7ab-84f7-dc0f-0c01-5fda13e447d5@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox