Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Support multi-statement transactions #87
Currently when attempting to execute a query within a transaction, the following output is produced:
Since transactions are not supported, and only single
Which use-case are you more interested in?
Though transactions are one way of handling bulk ingest, this could also be addressed with better
It's worth mentioning that a single PostgreSQL box does not scale well to many writers—no matter how many cores—due to existing issues with contention around buffer locking, etc. But because
The use case that has the most utility is a multi-statement transaction targeting the master and cascading to the child shards.
However, the primary problem is that
Anyone using a connection with autocommit disabled won't be compatible with any
django and peewee use transactions by default as well and i am not even sure yet you are able to disable this behavior as it may be even a psycopg2 or psycopg2cffi thing. And i just rewrote the hole stack for postgres because mongodb sucks BADLY if you go over 100m rows.
@jasonmp85 I have a use case for Multi-statement transactions targeting a single shard:
I think voltdb is the only solution at the moment that scales like nosql and it is simple to implement.
More info about ES+CQRS: