From: | Andrew Kerber <andrew(dot)kerber(at)gmail(dot)com> |
---|---|
To: | Evan Rempel <erempel(at)uvic(dot)ca> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: how to manage automatic updates |
Date: | 2018-01-03 18:50:50 |
Message-ID: | CAJvnOJYtGkmNEtUOA45oYe1yubzkmQrxm3=V6Z2EDr5obuXHug@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
You should never allow updates to be applied automatically to production
critical data. Period.
On Wed, Jan 3, 2018 at 12:39 PM, Evan Rempel <erempel(at)uvic(dot)ca> wrote:
>
> I'm giving some thought to scheduling automated updates of our PostgreSQL
> servers including the OS and application.
>
> Updating the PostgreSQL executable is easy with the RPM repository that
> the PorstgreSQL community provides, but some of
> the updates require changes to the system tables, stored procedures or
> other elements that reside in the database data. These
> updates are not included in the RPM updates (for good reason) so they are
> missed if only RPM updates are performed.
>
> Is there a best practice for applying database updates in an automated
> fashion?
>
> Does anyone want to share what they are doing regarding automated database
> updates with regards to updating data?
>
> Thanks for listening.
>
> Evan.
>
>
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Bolt | 2018-01-03 19:11:09 | Failed to execute pg_dump |
Previous Message | Evan Rempel | 2018-01-03 18:39:35 | how to manage automatic updates |