Common mistakes of DBAs
summary
Founder-run Postgres service with 12 years of experience lists concrete DBA failures and fixes: rely on a 3-2-1 backups approach with standby servers in separate availability zones, one copy on a file share, and mandatory verify restores to prove recoverability; enforce least-privilege roles and clear responsibilities for security; deploy monitoring tools and small scripts that trigger action before incidents; design schema and queries to match workloads so 90% of issues disappear; automate repetitive tasks and keep OS and DB patches current.
AI-written summary · about
related talks
44mBridging the Gap: The Vital Role of DBAs while contributing to the DevOps Culture
46mPostgres Platform "Best Practices" for the Modern DBA
34mDo we really need a DBA to manage our PostgreSQL databases on DBaaS
01mAre you an "accidental" DBA?
53mTop Development Mistakes When Working with PostgreSQL
01h 00mThe 10 Deadly PostgreSQL Sins
50mTransforming Your DBA Team Into a DBRE/SRE One!
26mNavigating Managed Databases for Over a Decade as a Non-DBA