| From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: dbmirror revisions |
| Date: | 2003-04-05 07:40:43 |
| Message-ID: | 200304050040.43856.pgsql@bluepolka.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Thursday April 3 2003 4:37, some yahoo wrote:
> * Eliminated bug in transaction ordering for replay. Updates
> cannot be replicated in the order of the transactions (see archives for
> discussion of why).
Upon further review, this bug report was the result of a misunderstanding of
the replication ordering. Both replication orderings, old and new, seem to
work fine so far.
Ed
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ed L. | 2003-04-05 08:28:15 | Re: dbmirror revisions |
| Previous Message | Tom Lane | 2003-04-05 05:01:51 | Re: Simpler question about timestamp |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kurt Roeckx | 2003-04-05 12:34:24 | Re: Stuff that doesn't work yet in IPv6 patch |
| Previous Message | Tom Lane | 2003-04-05 04:13:04 | Re: Detecting corrupted pages earlier |