----- Original Message ----- From: "Jeroen T. Vermeulen" <[EMAIL PROTECTED]>
> > I see a race condition in this approach: if you reconnect too fast, and the > > backend which actually should commit is still in progress (assume it takes a > > while to commit for whatever reasons) you get the impression that it did not > > commit - and a short time later the backend will commit... (before noticing > > that the client connection was lost). > > Good point. So far I assumed that a broken connection would take a while > to repair. OTOH by the time TCP gives up due to a bad network connection, > wouldn't the server reach the same conclusion? > Well, I wouldn't rely solely on TCP when assuring consistency. Also, I don't think that the backend will ever inspect its TCP socket while committing. btw: There could be also other reasons for the client to loose the connection (i.e. client process crashes). - Christian ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
