-
currently, all postgres transactions are run in `REPEATABLE READ` isolation level, which is almost certainly more than we really need. The difficulty is the need to audit all of our transactions to ch…
-
I noticed this while trying to use `node-postgres` with some integration tests. For the tests I needed to load in fixtures (that we normally loaded with `psql` in k8s) in test code. I read the `.sql` …
-
I've started getting "could not serialize access due to read/write dependencies among transactions" on the transactions that used to work fine. I use Go client, and I'm not sure if this error is relat…
divan updated
2 months ago
-
**Describe the bug**
On Postgres (`TransactionsContextPooled`) using more then one level of nested sub-transactions cause a deadlock.
All returned instances of `NestedTransactionPooledContext` in `_…
-
Currently, QueryAPI uses two simultaneous Postgres pooling. One is pgBouncer and the other is PgPool. The latter is a code level connection pooler which is potentially no longer necessary. The removal…
-
Debate-map should be more resilient to concurrent update commands. (which sometimes cause claimminer map generations to fail)
So for example:
* We could reduce the isolation level for the transact…
-
### Describe the bug
Having XA enabled in a Quarkus app (with `quarkus.datasource.jdbc.transactions=xa` in the `application.properties`), and invoking two XA datasources in a `@Transactional` metho…
-
Reference:
https://vertx.io/docs/apidocs/io/vertx/ext/sql/SQLOptions.html#getTransactionIsolation--
https://vertx.io/docs/apidocs/io/vertx/ext/sql/TransactionIsolation.html
-
Please ensure you do the following when reporting a bug:
- [x] Provide a concise description of what the bug is.
- [x] Provide information about your environment.
- [x] Provide clear steps to reprodu…
-
Ambiguous errors (which could be generated internally to CRDB or a result of network failure between the gateway and client) are difficult to handle. Either the application takes care to make its tran…