From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, pgsql-hackers@postgresql.org
Subject: Re: SIGSEGV in BRIN autosummarize
In-reply-to: <20171017122922.GC13880@telsasoft.com>
References: <20171014224220.GB22678@telsasoft.com>
 <20171017105916.3rvmznxnuphn3uph@alvherre.pgsql>
 <20171017122922.GC13880@telsasoft.com>
Comments: In-reply-to Justin Pryzby <pryzby@telsasoft.com>
	message dated "Tue, 17 Oct 2017 07:29:22 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5647.1508247264.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 17 Oct 2017 09:34:24 -0400
Message-ID: <5648.1508247264@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Justin Pryzby <pryzby@telsasoft.com> writes:
> 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 environm=
ent
> (althought nothing so important that the crashes are a serious concern ei=
ther).

> Is it reasonable to wget the postgres tarball, apply the patch, and run t=
he
> compiled postgres binary from the source tree, without running make insta=
ll or
> similar ?  Otherwise, would it be good enough to copy the postgres binary=
 to
> /usr/pgsql-10/bin (and reinstall the binary package later) ?

The trick in this sort of situation is to make sure you build binaries
that match your existing install in every way except having the added
patch, and maybe getting installed into a different directory.

So: where did you get the existing binaries?  If it's from some vendor
packaging system, what you should do is fetch the package source, add
the patch to the probably-nonempty set of patches the vendor is applying,
and rebuild your own custom package version.  If you haven't done that
before, it's a good skill to acquire ...

			regards, tom lane


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