Re: error code 25001

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: error code 25001
Date: 2009-01-07 13:30:01
Message-ID: 22745.1231335001@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tatsuo Ishii <ishii(at)postgresql(dot)org> writes:
> Error code 25001 is used for "SET TRANSACTION ISOLATION LEVEL must be
> called before any query" when it's an ERROR. However, it also means
> "there is already a transaction in progress" when it's a NOTICE.

> So we cannot distinguish them just by checking the error code.

> So my question is, an error code is used for both an error condition
> *and* a warning: is this normal?

I don't think that's the only case. Surely it's not that hard to tell
whether you have an error or not ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2009-01-07 13:39:42 Re: Do we still need constraint_exclusion?
Previous Message Magnus Hagander 2009-01-07 13:25:01 Re: Solve a problem of LC_TIME of windows.