3 ms·
I don’t know. But I do know that whatever the question, Postgres is the answer.
by andrewstuart 4y ago
I don’t know.
But I do know that whatever the question, Postgres is the answer.
- revskill 4y agoAnswer belongs to the user. Postgres is just one good tool.
- pjmlp 4y agoDistributed transactions across a database cluster?
- rastignack 4y agoYou can do it with extensions. However most of the time you are not going to need it.
- pjmlp 4y agoAh so it isn't the answer for everything.
- valenterry 4y agoDownvoted for blasphemy
- valenterry 4y agoReplying to myself so that you can pay me back
- johnthescott 4y agotrue. what IS the answer for everything, by the way?
- voytec 4y ago42.
- CuriouslyC 4y agoForeign data wrappers. "During a query that references any remote tables on a foreign server, postgres_fdw opens a transaction on the remote server if one is not already open corresponding to the current local transaction. The remote transaction is committed or aborted when the local transaction commits or aborts. Savepoints are similarly managed by creating corresponding remote savepoints."
- riku_iki 4y agodoes it support two-phase commit? What if local transaction succeeded, and remote failed? Cluster will have inconsistent data?..
- CuriouslyC 4y agoThe mental model is slightly different. FDWS are basically server -> server linkages, not literally clustering. As a result, data consistency between servers is less of an issue - the data is likely to only live in one place (read replicas and failovers notwithstanding). There may be some error handling and try/rollback around remote transactions baked into postgres_fdw but I'm not familiar enough to say.
- johnthescott 4y agothe citus extension might be your friend.