From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, 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:59:32 |
Message-ID: | 8656d7ab-84f7-dc0f-0c01-5fda13e447d5@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-10-17 13:16:20 | Re: PATCH: enabling parallel execution for cursors explicitly (experimental) |
Previous Message | Justin Pryzby | 2017-10-17 12:49:24 | Re: SIGSEGV in BRIN autosummarize |