From: | Jun Ishiduka <ishizuka(dot)jun(at)po(dot)ntts(dot)co(dot)jp> |
---|---|
To: | masao(dot)fujii(at)gmail(dot)com, ssinger_pg(at)sympatico(dot)ca, magnus(at)hagander(dot)net, robertmhaas(at)gmail(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org, cedric(dot)villemain(dot)debian(at)gmail(dot)com, heikki(dot)linnakangas(at)enterprisedb(dot)com |
Subject: | Re: Online base backup from the hot-standby |
Date: | 2011-10-09 18:04:25 |
Message-ID: | 201110091805.p99I5bva012434@ccmds32.silk.ntts.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I created a patch corresponding FPW.
Fujii's patch (ver 9) is based.
Manage own FPW in shared-memory (on master)
* startup and walwriter process update it. startup initializes it
after REDO. walwriter updates it when started or received SIGHUP.
Insert WAL including a value of current FPW (on master)
* In the the same timing as update, they insert WAL (is named
XLOG_FPW_CHANGE). XLOG_FPW_CHANGE has a value of the changed FPW.
* When it creates CHECKPOINT, it adds a value of current FPW to the
CHECKPOINT WAL.
Manage master's FPW in local-memory in startup (on standby)
* It takes a value of the master's FPW by reading XLOG_FPW_CHANGE at
REDO.
Check when pg_start_backup/pg_stop_backup (on standby)
* It checks to use these two value.
* master's FPW at latest CHECKPOINT
* current master's FPW by XLOG_FPW_CHANGE
Regards.
--------------------------------------------
Jun Ishizuka
NTT Software Corporation
TEL:045-317-7018
E-Mail: ishizuka(dot)jun(at)po(dot)ntts(dot)co(dot)jp
--------------------------------------------
Attachment | Content-Type | Size |
---|---|---|
standby_online_backup_09base_01fpw.patch | application/octet-stream | 12.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2011-10-09 18:40:10 | Re: libpq, PQdescribePrepared -> PQftype, PQfmod, no PQnullable |
Previous Message | Alex Hunsaker | 2011-10-09 17:56:08 | Re: alter table only ... drop constraint broken in HEAD |