PostgreSQL Administratoren Albtraum

Probleme mit PostgreSQL

• Viele Forks, Cloud-Varianten, Erweiterungen (Extensions) und Distributoren.
• Core Team und Major Contributors: EnterpriseDB (EDB), Amazon Web Services (AWS) und Microsoft (MS).
• Nicht alle Erweiterungen sind produktionstauglich.
• PostgreSQL major version upgrades are hard (up to at least to PostgreSQL 17!).
• Replicas require identical O/S package versions!
• Collation dependency on O/S (solved in PostgreSQL 17?).
• Schlechte MVCC Implementation: The Part of PostgreSQL We Hate the Most, Yes, PostgreSQL Has Problems. But We’re Sticking With It!.
• XID Counter Overflow -> Data loss.
• Vacuum.
• Changing shared_buffers requires database (cluster) restart! Source: https://www.postgresql.org/docs/current/runtime-config-resource.html
• Implementierung von Index Clustered Tables (Index Organized Tables): Tabelle muss “reclustered” werden: PostgreSQL Documentation: CLUSTER, Stackoverflow: About clustered index in postgres

Weitere Quellen

Siehe auch:

• Is PostgreSQL catching up with the Oracle Database?
• Why would you say MySQL/Maria/et al are easier to maintain for simple apps than PG?
• Jobin Augustine, Percona, 2025-01-14: What Hurts in PostgreSQL Part One: Temporary Tables
• Greg Sabino Mullane, Crunchy Data, 2025-01-27: When Does ALTER TABLE Require a Rewrite?
• See also ’table rewrite’ here: https://www.postgresql.org/docs/current/sql-altertable.html