Hi Brian!
I got a patch to fix this. Unfortunately, I'm having some problems with
github at this moment and I couldn't push it to create a pull request.
Would you mind to patch a local copy of Npgsql code and give it a try?
Here is the patch:
diff --git a/Npgsql/Npgsql/NpgsqlConnector.cs
I feel dumb asking this question, but I can't seem to find the answer online.
I'm running serializable transactions, and so naturally, they will
sometimes fail with the error could not serialize access due to
concurrent update.
But then I try to issue a ROLLBACK so I can continue using the
On Mon, Mar 10, 2014 at 1:41 PM, Brian Crowell br...@fluggo.com wrote:
I feel dumb asking this question, but I can't seem to find the answer
online.
I'm running serializable transactions, and so naturally, they will
sometimes fail with the error could not serialize access due to
concurrent
On Mon, Mar 10, 2014 at 4:16 PM, Jeff Janes jeff.ja...@gmail.com wrote:
... Or maybe it is mangling the ROLLBACK; into some form
the database doesn't recognize. Look in the postgres log files to see what
the events look like from PostgreSQL's perspective.
Well that's the clue I needed. I was
