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?
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.
