Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Postgres Is the New Default

Ines Sombra
September 19, 2012

Postgres Is the New Default

Postgres is the new default – How we transitioned our platform at Engine Yard and why you should too.

Given at Postgres Open 2012. Video is available here: http://www.youtube.com/watch?v=sFfJjfOk9NA

Ines Sombra

September 19, 2012
Tweet

More Decks by Ines Sombra

Other Decks in Technology

Transcript

  1. Agenda • Where we were • Our relationship with Postgres

    • Challenges • Our future together
  2. Engine Yard Cloud • Only MySQL 5.0 • 8.3 in

    perpetual Alpha • No Slaves, No Docs • Increasing interest • Stack Expansion - DIRTT
  3. Why love Postgres? • Flexible Replication: streaming & hot standby

    • Features & Extensions • Versatile Data Types • FDWs
  4. Why love Postgres? • All of the Indexes! • B-tree,

    GiST, GIN, SP-Gist* • Procedural Languages (PL) • Full-Text Search
  5. Why love Postgres? • Feature parity with Managed • Outstanding

    community & commercial support • Let’s make it our default!
  6. Roadmap issues • Shiny new process for DB releases •

    Alpha, Beta, GA • Surprise we got it WRONG!
  7. Multiple Architectures • EBS Volumes & 32-bit instance sizes •

    Dump & Restore only way to vertically scale
  8. Installation • Engine Yard Cloud • Chef > EBS •

    Engine Yard Managed • Puppet > Storage
  9. Configuration • $PGDATA on EBS • We don’t RAID •

    Snapshots to S3 • pg_xlog same volume
  10. Backups • Internal tool wraps around pg_dump • Snapshots &

    dumps to S3 • Only backup from slave (if present)
  11. Allow Extensions • Dedicated instances • Customizations OK! • Ship

    recipes for ~30 extensions • Curated & tested
  12. Future Directions • 9.2 Support • AWS Optimizations • Provisioned

    IOPS • EBS optimized instances • SSD-backed instances
  13. Future Directions • Customer education still a problem • Low

    adoption of slaves • ~146 year ago • ~165 now