Re: BUG #6497: Error sent to client, but data written anyway

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christophe Pettus <xof(at)thebuild(dot)com>
Cc: Ryan Lowe <rlowe(at)pablowe(dot)net>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6497: Error sent to client, but data written anyway
Date: 2012-02-29 21:27:57
Message-ID: 8238.1330550877@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Christophe Pettus <xof(at)thebuild(dot)com> writes:
> On Feb 29, 2012, at 1:15 PM, Tom Lane wrote:
>> But there's a quite separate question as to
>> whether the behavior Ryan is claiming for a pre-commit crash is actually
>> possible. I don't believe it, and I failed to reproduce his test
>> scenario.

> Did you check it with killing the postmaster (as Ryan was) as opposed to the backend?

I tried both, and got the expected (though different) results both
ways. See my previous response.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message k/a 2012-02-29 22:25:30 Re: BUG #6498: with recursive / union all
Previous Message Christophe Pettus 2012-02-29 21:22:43 Re: BUG #6497: Error sent to client, but data written anyway