| From: | Dan Smith <j(dot)daniel(dot)smith1(at)gmail(dot)com> |
|---|---|
| To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Automation |
| Date: | 2023-10-11 16:15:03 |
| Message-ID: | CAK50JryZLE+nmL3TWPD_mtJnMfcUdEDikrBw+H6i=2VofKstiQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi Rajesh,
I agree with previous comments about this being pretty vague. Here are
some general ideas though:
- Automate backups if applicable
- Automate fail-over if applicable
- Use Infrastructure / Configuration as Code
- Use Schema Migrations
- Implement CI/CD pipelines with static analysis (such as linting /
anti-pattern checking) and automated testing.
Beyond these basics, I think people would really need to know what problem
you are trying to solve. There's no point in automating a solution if the
problem isn't defined and understood. Further, many solutions are really
going to depend on your environment.
Best regards,
Dan Smith
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2023-10-11 16:27:30 | Re: Automation |
| Previous Message | Ron | 2023-10-11 15:52:36 | Re: Automation |