From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
Cc: | Liam Lesboch <liamlesboch(at)hotmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Replication options? |
Date: | 2004-09-25 22:26:17 |
Message-ID: | 4155F089.40200@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>>> logging of the commit is done after the WAL operation, it must be
>>> assured that WAL replay during crash recovery also causes
>>> replication log journal to be recovered or repeated. In short, the
>>> replication log must be covered by the same redo mechanism the crash
>>> recovery system uses.
>>
>>
>> This I will have to verify with our programmers as to exactly "when"
>> the replication occurs.
>
>
> Joshua,
>
> you never followed up to this one.
As of 1.3.1 (the current version) we also perform wal processing to
insure that the transaction is correctly replicated in case of a crash.
Sincerely,
Joshua D. Drake
>
>
> Jan
>
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Allison | 2004-09-25 23:04:05 | serial data type |
Previous Message | TroyGeek | 2004-09-25 21:26:35 | SMgrRelation hashtable corrupted |