Re: Transactions over pathological TCP connections - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Transactions over pathological TCP connections
Date
Msg-id CA+TgmoanfeGDdyFkFBx7WCnMv64u6Zoz+-gKUrL-K-=AU7NE+w@mail.gmail.com
Whole thread Raw
In response to Re: Transactions over pathological TCP connections  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Transactions over pathological TCP connections  (Leon Smith <leon.p.smith@gmail.com>)
List pgsql-hackers
On Tue, Jun 19, 2012 at 1:56 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> The transaction would be committed before a command success report is
> delivered to the client, so I don't think delivered-and-not-marked is
> possible.

...unless you have configured synchronous_commit=off, or fsync=off.

Or unless your disk melts into a heap of slag and you have to restore
from backup.  You can protect against that last case using synchronous
replication.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Skip checkpoint on promoting from streaming replication
Next
From: Tom Lane
Date:
Subject: Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node