Synchronous replication patch v4

Поиск
Список
Период
Сортировка
От Fujii Masao
Тема Synchronous replication patch v4
Дата
Msg-id 3f0b79eb0811271845l4a8e4a20ga519aefc2a4d5162@mail.gmail.com
обсуждение исходный текст
Список pgsql-hackers
Hello,

I chaged the patch accoding to the comment against v3 and fixed
some bugs. Since I failed to post the patch because of the excess
of mail size, I would attach it to Wiki from this time.
http://wiki.postgresql.org/wiki/NTT%27s_Development_Projects#Patch_set

List of updates
--------------------
* Rename the database for replication from "walsender" to"replication".

* Change the way to treat "replication" database so that the normalclient can connect and query to it. So, in order to
startreplication,it's necessary to connect to "replication" database and send theparticular message.
 

* Disable skipping-WAL optimization during replication like WALarchiving.

* Push RequestXLogSend and WaitXLogSend into XLogFlush tosimplify the code.

* Re-define replication_timeout as PGC_SUSET to prevent thenon-superuser from stopping replication easily.

* Change the logic to forbid the startup process from trying to redothe WAL which walreceiver has not received yet.
Thishappenswhen the trigger file of pg_standby is created while walreceiveris alive. Before the startup process get
overthe WAL positionwhere walreceiver has not reached at yet, walreceiver certainlyexits.
 

* Integrate the logic to start replication between walsender andwalreceiver in order to simplify the code.

* Change walsender and walreceiver to display the replicationstarting / ending position when replication starts /
ends.

* Skip recycling the restored WAL file if it's a symbolic link.

* Re-zero the page if needed before walreceiver writes the WALto disk.

* Add new trigger file option into pg_standby, which can promotethe standby to the primary without any transaction
loss.http://archives.postgresql.org/pgsql-hackers/2008-11/msg01638.php

I shelved the change for pg_standby to get over the gap of
timeline this time, because the consensus is not reached.
http://archives.postgresql.org/pgsql-hackers/2008-11/msg01612.php

If you notice anything, please feel free to comment!

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: [PATCHES] GIN improvements
Следующее
От: "Fujii Masao"
Дата:
Сообщение: Re: Comments to Synchronous replication patch v3