Re: Recovering from failed transaction

From: Brian Crowell <brian(at)fluggo(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Recovering from failed transaction
Date: 2014-03-10 21:49:28
Message-ID: CAAQkdDqaM0j1JhEy+aXsNVNOvOD1R5DDOm-HtdiwfQ+sVw6WbA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Mar 10, 2014 at 4:16 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)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 misinterpreting Postgres's log
file; it was complaining about the "SET statement_timeout" statement
Npgsql was slipping ahead of my ROLLBACK. Apparently I need to do
transactions with Npgsql's transaction class.

--Brian

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Venkata Balaji Nagothi 2014-03-10 23:03:05 Re: bg writer went away after reload
Previous Message Matthew Chambers 2014-03-10 21:30:22 bg writer went away after reload