From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Shantanu Shekhar <shekharshan(at)yahoo(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Postgres automatic minor version upgrade |
Date: | 2020-08-12 14:26:07 |
Message-ID: | 76218c72-8e55-4fc8-0363-d12603011f74@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/12/20 5:46 AM, Shantanu Shekhar wrote:
> Hello,
>
> We are using Postgres 11.6 through AWS relational database service. As
> part of its RDS service AWS offers automatic minor version upgrade. If
> we turn this setting on the minor versions will get upgraded without us
> even knowing about it. We are in a security sensitive vertical so we
> would like to ensure we don't miss out on critical security patches and
> bug fixes. We also use AWS Multi Availability Zones which I believe is
> built upon Postgres hot standby HA feature.
>
> We are not very clear on what are the possible risks we may be opening
> ourselves up to if we did automatic minor version. I would appreciate
> any suggestions on how to go about understanding the potential risks
> with using automatic minor version upgrade.
https://aws.amazon.com/premiumsupport/
>
> Thanks,
>
> Shantanu
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2020-08-12 16:01:06 | Re: insert on conflict postgres returning distinction |
Previous Message | pinker | 2020-08-12 14:23:04 | insert on conflict postgres returning distinction |