Kicking the Donkey of PostgreSQL Replication
This is the title of a talk I am developing for the matured PostgreSQL Conference: PGConf NYC 2014 . Formerly a PgDay, this is now a full blown conference extending two days with three tracks. From all reports it is set to be the largest PostgreSQL Conference ever in the United States, surpassing even the old West and East series (which no conference in the U.S. has done to date). It is truly exciting times for our community.

This talk will be a departure from my standby talks of PostgreSQL Performance and Choosing the right hardware. Katz asked me, "to bring your full East Coast from the West Coast personality.". I plan on doing so. So cinch up the boot straps it is going to be a ride. In classic JD style I am going to be blunt and to the point about the good, the bad, and the, "WTH were they thinking" of PostgreSQL Replication.

So outside of personality what am I really trying to deliver to the community? I think the description of the talk says it all:

  • Have you ever wondered how to configure PostgreSQL Replication?
  • Have you ever wondered how to configure PostgreSQL Log Shipping?
  • Have you ever wondered: Which one is best for my application?
  • Are you aware of the pitfalls of Replication? Where it breaks? When it will act in a way that is counter-intuitive? Do you know how to fix it?
  • Do you know how to monitor it?

If you have asked yourself any of these questions, this is the talk for you. We will step through PostgreSQL replication, the technology involved, the configuration parameters and how to configure it in a manner that isn't fragile. We will also cover gotcha's how to prepare for them and understanding what replication is doing.

This talk is not not for the faint of heart. I will take a no holds barred approach and give you the real deal, the dirt and the gold that is one of the most sought after PostgreSQL features.

On a closing note, this conference is showing how a PostgreSQL User Group, combined with the resources of United States PostgreSQL can help grow and educate the community. They don't just help NYCPUG, they also help PDXPUG, PHILLYPUG and SEAPUG. Maybe your PUG should consider working with PgUS? If so, give "Jonathan S. Katz" [jonathan.katz {@} excoventures.com] a jingle.