Re: Two weeks to feature freeze

From: Mike Mascari <mascarm(at)mascari(dot)com>
To: Mike Mascari <mascarm(at)mascari(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Two weeks to feature freeze
Date: 2003-06-23 06:46:51
Message-ID: 3EF6A25B.9060105@mascari.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:

> Tom Lane wrote:
>
>>Basically, the subordinate must be willing to hold its breath *forever*.
>
>
> Yep. And if the cohort crashes while waiting for the coordinator to
> come back on-line, if I understand the world correctly, it must be
> capable of committing the database changes associated with the
> COMMIT-VOTE response it supplied to the coordinator's PREPARE. It
> seems this would require REDO? And yet there are thousands of
> installed distributed databases running enterprises every day.

Please ignore the REDO remark. It's late where I am...

Mike Mascari
mascarm(at)mascari(dot)com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Enke, Michael 2003-06-23 08:02:46 Re: [HACKERS] again: Bug #943: Server-Encoding from EUC_TW toUTF-8
Previous Message Bruce Momjian 2003-06-23 06:09:10 Re: [HACKERS] MARKED_FOR_UPDATE && XMAX_COMMITTED == XMAX_INVALID ?