PostgreSQL Replication
The cluster focuses on discussions about PostgreSQL's replication features, including synchronous replication, WAL shipping, logical replication, master-master setups, and tools like Bucardo, BDR, and repmgr, often comparing them to MySQL or questioning their suitability for high availability and scaling.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Well Postgres has sync replication if you value consistency
Don't Maria, Postgres, etc make replication pretty easy?
Nicer replication story? Try recent postgres with wal shipping + wal streaming;)
The post touches upon it, but I didn't really understand the point. Why doesn't synchronous replication in Postgres work for this use case? With synchronous replication you have a primary and secondary. Your queries go to the primary and the secondary is guaranteed to be at least as up to date as the primary. That way if the primary goes down, you can query the secondary instead and not lose any data.
They say they use master-master replication with mysql so they have no single points of failures. Back then, I think the only option with postgres was to use slony.
Pgpool replication can work that way too
Why isn't the built-in master/slave replication plus WAL archiving to something like S3 sufficient?
Seems very useful. This stuff can’t be done already with pg replication?
Try it with synchronous replication (I want that for my main db) and report back.
How is the replication / master-master / scale-out for this database? We really would love a solution like this but it would need to scale for our use case.