pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedAutomation
7+ messages / 5 participants
[nested] [flat]
* Automation
@ 2023-10-11 15:36 Rajesh Kumar <rajeshkumar.dba09@gmail.com>
0 siblings, 3 replies; 7+ messages in thread
From: Rajesh Kumar @ 2023-10-11 15:36 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
I have been asked to do some of automation as a postgres dba. I have only
one year exp as dba.
Help me with some hints of what kind of automation I can do here in a
simple postgres setup.
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Automation
@ 2023-10-11 15:52 Ron <ronljohnsonjr@gmail.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2 siblings, 0 replies; 7+ messages in thread
From: Ron @ 2023-10-11 15:52 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
On 10/11/23 10:36, Rajesh Kumar wrote:
> I have been asked to do some of automation as a postgres dba. I have only
> one year exp as dba.
"Some automation" is pretty ambiguous.
> Help me with some hints of what kind of automation I can do here in a
> simple postgres setup.
What are you already doing?
--
Born in Arizona, moved to Babylonia.
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Automation
@ 2023-10-11 16:15 Dan Smith <j.daniel.smith1@gmail.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2 siblings, 0 replies; 7+ messages in thread
From: Dan Smith @ 2023-10-11 16:15 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
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
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Automation
@ 2023-10-11 16:27 David G. Johnston <david.g.johnston@gmail.com>
parent: Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2 siblings, 2 replies; 7+ messages in thread
From: David G. Johnston @ 2023-10-11 16:27 UTC (permalink / raw)
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
On Wed, Oct 11, 2023 at 8:42 AM Rajesh Kumar <rajeshkumar.dba09@gmail.com>
wrote:
> Help me with some hints of what kind of automation I can do here in a
> simple postgres setup.
>
I would suggest you find at least one good reference book on PostgreSQL
administration that covers everything involved with being a DBA. You will
need to be aware of those regardless of automation you may choose to
implement to avoid doing them manually. Also, automated metric collection
tends to be important, and setting appropriate alerts (this include OS
system administration scoped stuff like disk space) - regardless of
whether you'd want to automated or manually resolve any events raised by
those tools.
David J.
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Automation
@ 2023-10-11 16:43 Matuszyk, Paul G. <matuszyk@matuszyk.com>
parent: David G. Johnston <david.g.johnston@gmail.com>
1 sibling, 1 reply; 7+ messages in thread
From: Matuszyk, Paul G. @ 2023-10-11 16:43 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Hi
On top of that pretty good rule for automation is - automate any activity
which you need to do more than 3 times e.g.
- backups
- restores
- migrations
- monitoring
- log checking
Regards
Paul G. Matuszyk
All the views expressed in this email are mine, and do not necessarily
represent those of my client (or possibly anyone else in the known
universe). No animals were harmed in the creation of this message. May
contain nuts. In order to preserve the world's resources, this email was
composed from refurbished pixels recycled from previously-used emails.
Ingredients: E-113, E-120, E-9999, EI-EI-O. If you have read this far -
don't you have anything better to do with your time?
On Wed, 11 Oct 2023 at 18:27, David G. Johnston <david.g.johnston@gmail.com>
wrote:
> On Wed, Oct 11, 2023 at 8:42 AM Rajesh Kumar <rajeshkumar.dba09@gmail.com>
> wrote:
>
>> Help me with some hints of what kind of automation I can do here in a
>> simple postgres setup.
>>
>
> I would suggest you find at least one good reference book on PostgreSQL
> administration that covers everything involved with being a DBA. You will
> need to be aware of those regardless of automation you may choose to
> implement to avoid doing them manually. Also, automated metric collection
> tends to be important, and setting appropriate alerts (this include OS
> system administration scoped stuff like disk space) - regardless of
> whether you'd want to automated or manually resolve any events raised by
> those tools.
>
> David J.
>
>
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Automation
@ 2023-10-11 18:36 Rajesh Kumar <rajeshkumar.dba09@gmail.com>
parent: David G. Johnston <david.g.johnston@gmail.com>
1 sibling, 0 replies; 7+ messages in thread
From: Rajesh Kumar @ 2023-10-11 18:36 UTC (permalink / raw)
To: David G. Johnston <david.g.johnston@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Thanks, I'll check them out.
On Wed, 11 Oct, 2023, 9:57 PM David G. Johnston, <david.g.johnston@gmail.com>
wrote:
> On Wed, Oct 11, 2023 at 8:42 AM Rajesh Kumar <rajeshkumar.dba09@gmail.com>
> wrote:
>
>> Help me with some hints of what kind of automation I can do here in a
>> simple postgres setup.
>>
>
> I would suggest you find at least one good reference book on PostgreSQL
> administration that covers everything involved with being a DBA. You will
> need to be aware of those regardless of automation you may choose to
> implement to avoid doing them manually. Also, automated metric collection
> tends to be important, and setting appropriate alerts (this include OS
> system administration scoped stuff like disk space) - regardless of
> whether you'd want to automated or manually resolve any events raised by
> those tools.
>
> David J.
>
>
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Automation
@ 2023-10-13 08:51 Rajesh Kumar <rajeshkumar.dba09@gmail.com>
parent: Matuszyk, Paul G. <matuszyk@matuszyk.com>
0 siblings, 0 replies; 7+ messages in thread
From: Rajesh Kumar @ 2023-10-13 08:51 UTC (permalink / raw)
To: Matuszyk, Paul G. <matuszyk@matuszyk.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Thank you
On Fri, 13 Oct, 2023, 2:15 PM Matuszyk, Paul G., <matuszyk@matuszyk.com>
wrote:
> Hi
>
> On top of that pretty good rule for automation is - automate any activity
> which you need to do more than 3 times e.g.
> - backups
> - restores
> - migrations
> - monitoring
> - log checking
>
> Regards
> Paul G. Matuszyk
>
> All the views expressed in this email are mine, and do not necessarily
> represent those of my client (or possibly anyone else in the known
> universe). No animals were harmed in the creation of this message. May
> contain nuts. In order to preserve the world's resources, this email was
> composed from refurbished pixels recycled from previously-used emails.
> Ingredients: E-113, E-120, E-9999, EI-EI-O. If you have read this far -
> don't you have anything better to do with your time?
>
>
> On Wed, 11 Oct 2023 at 18:27, David G. Johnston <
> david.g.johnston@gmail.com> wrote:
>
>> On Wed, Oct 11, 2023 at 8:42 AM Rajesh Kumar <rajeshkumar.dba09@gmail.com>
>> wrote:
>>
>>> Help me with some hints of what kind of automation I can do here in a
>>> simple postgres setup.
>>>
>>
>> I would suggest you find at least one good reference book on PostgreSQL
>> administration that covers everything involved with being a DBA. You will
>> need to be aware of those regardless of automation you may choose to
>> implement to avoid doing them manually. Also, automated metric collection
>> tends to be important, and setting appropriate alerts (this include OS
>> system administration scoped stuff like disk space) - regardless of
>> whether you'd want to automated or manually resolve any events raised by
>> those tools.
>>
>> David J.
>>
>>
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2023-10-13 08:51 UTC | newest]
Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-10-11 15:36 Automation Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2023-10-11 15:52 ` Ron <ronljohnsonjr@gmail.com>
2023-10-11 16:15 ` Dan Smith <j.daniel.smith1@gmail.com>
2023-10-11 16:27 ` David G. Johnston <david.g.johnston@gmail.com>
2023-10-11 16:43 ` Matuszyk, Paul G. <matuszyk@matuszyk.com>
2023-10-13 08:51 ` Rajesh Kumar <rajeshkumar.dba09@gmail.com>
2023-10-11 18:36 ` Rajesh Kumar <rajeshkumar.dba09@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox