Re: A bad behavior under autocommit off mode

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: A bad behavior under autocommit off mode
Date: 2003-03-20 23:48:06
Message-ID: 3E7A5336.E009C2B@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
> Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> > My proposal also fixes the bug though Tom objected to it.
>
> I've forgotten what your proposal was?

Because WARNING isn't an ERROR, treat it in the same way
as NORMAL, i.e after the WARNING, simply set the blockState
to TBLOCK_END without calling AbortTransaction. Also
remove the WARNING in case of autocommit off mode.

regards,
Hiroshi Inoue
http://www.geocities.jp/inocchichichi/psqlodbc/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2003-03-21 02:11:31 probs with postgres
Previous Message Philip Warner 2003-03-20 23:36:58 Re: Varchar Vs. Text index matching - why different?