From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | "Patil, Prashant" <Prashant(dot)Patil(at)crowncastle(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Postgres Security Patches Question |
Date: | 2019-04-24 15:17:18 |
Message-ID: | 20190424151718.GA6771@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2019-Apr-24, Patil, Prashant wrote:
> Thanks Tom. So since security patches is not release separately, they
> are part of minor releases. Is this correct statement?
It is correct.
> If they are part minor releases, we need to download source code for
> that release and perform upgrade and while performing upgrade, we can
> point install directories to our custom data/config directories RIGHT?
The install directories don't have to care where your data/config
directories and files are. Only your start scripts have to. You can
just stop the database, install the new binaries on top of the previous
ones, start the database.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-04-24 19:59:04 | Re: Postgres Security Patches Question |
Previous Message | Patil, Prashant | 2019-04-24 15:09:35 | RE: Postgres Security Patches Question |