Skip site navigation (1) Skip section navigation (2)

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

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Ryan Lowe <rlowe(at)pablowe(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:05:20
Message-ID: B735DD60-9C56-41F5-BC34-3709A4A0BDE1@thebuild.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Feb 29, 2012, at 9:26 AM, Ryan Lowe wrote:

> Thanks for all the responses, but I think I'm being unclear here.

The point Tom was making is that this is indistinguishable from the scenario:

1. Client sends commit.
2. Server successfully commits data.
3. Server starts to write response.
4. Network fails.
5. Client receives abnormal disconnection response from its network connection to the server.

--
-- Christophe Pettus
   xof(at)thebuild(dot)com


In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2012-02-29 21:15:18
Subject: Re: BUG #6497: Error sent to client, but data written anyway
Previous:From: Tom LaneDate: 2012-02-29 20:48:48
Subject: Re: BUG #6498: with recursive / union all

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group