On 9/24/2004 5:12 PM, Tom Lane wrote:
This means either that the server sent a commit message before it had xlog'd the commit, or that Pgtcl mistakenly reported the command as successful when it was not. Any thoughts?
Is it somehow possible that the commit record was still sitting in the shared WAL buffers (unwritten) when the response got sent to the client? That would be the only possibility I can see right now, because Pgtcl used as in that script sits on top of libpq in blocking mode and that pretty much outrules early reporting of COMMAND_OK. Fsync/disk-flush issues can't be the case either because it was only a PM restart without any OS crash involved, and I don't like the idea of <whatever*nix> forgetting a write().
Jan
-- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== [EMAIL PROTECTED] #
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org
