Jason Petersen
Jason Petersen
So `pg_shard` is in the Yum repositories now, but I don't know what work is needed to get it into the Apt ones… I'll ask around.
# Question Which use-case are you more interested in? - Multi-statement transactions targeting a single shard - Multi-statement transactions spanning many shards # Atomicity `pg_shard` works well for applications that...
@digi604: It appears possible to disable transactions within `psycopg`. See [here](http://initd.org/psycopg/docs/usage.html#transactions-control) and [here](http://initd.org/psycopg/docs/connection.html#connection.commit) for more information.
Two quick questions to help define this feature: - In the ideal implementation of this feature, would the "prototype" table on the master also be dropped, or just its shards?...
Got it. You _don't_ want the master table dropped, so intercepting `DROP TABLE` is not ideal. Just a function to drop the shards (and their ephemera: sequences, constraints, etc.) from...
Thanks for the clear bug report and copy-paste repro case! One more thing for posterity's sake: what version of PostgreSQL were you testing this against?
This will be closed by #60.
I think the most difficult problem to overcome will be "what happens when a replica fails partway through", not "what happens when you can't send data to any replica". Do...
@marcocitus mentioned [pgloader](http://pgloader.io/) the other day… maybe we can look at it for inspiration re: partial failures or ignore-and-continue semantics.