From: | "Allan Sullivan" <allan(dot)sullivan(at)nortak(dot)com> |
---|---|
To: | <pgsql-novice(at)postgresql(dot)org> |
Subject: | Error 25P02 - transaction aborted - Potential causes? |
Date: | 2007-03-13 19:57:57 |
Message-ID: | 3D9BF154E1B04444B6D07D04B1F0CD4F5C0486@ntk-mail2k3.nortak.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
I've started to get the following error:
25P02 - current transaction is aborted, commands ignored
This error occurs on a 'select' statement done within a transaction, after multiple selects and updates have already been made. The application is written in VB.Net, and uses npgsql for data access. (I'm running postgres 8.2).
Does anyone have any idea what the cause of the error could be? Is there any chance that its because Postgres needs more space for doing rollbacks? (If so, how is this space increased).
Or, is there any change I can make to the way I do the transactions that will help? Currently, I'm using the following:
Dim conn As Npgsql.NpgsqlConnection
Dim Trans As Npgsql.NpgsqlTransaction
conn = New Npgsql.NpgsqlConnection("my connection string...")
conn.Open()
Trans = conn.BeginTransaction
Are there any parameters to the transaction that I can use that would prevent this error?
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-03-13 20:12:12 | Re: Error 25P02 - transaction aborted - Potential causes? |
Previous Message | Brian Hurt | 2007-03-13 18:41:49 | plpgsql: inserting a record into a (matching) table |