| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jun Ishiduka <ishizuka(dot)jun(at)po(dot)ntts(dot)co(dot)jp> |
| Cc: | cedric(dot)villemain(dot)debian(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Online base backup from the hot-standby |
| Date: | 2011-08-15 11:52:21 |
| Message-ID: | CA+TgmoYRKLsDSR6F4tDbgnvE-s7-BLNE+h=XeswRb3tpZs0KEA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2011/8/15 Jun Ishiduka <ishizuka(dot)jun(at)po(dot)ntts(dot)co(dot)jp>:
>> > * Not correspond yet
>> >
>> > * full_page_write = off
>> > -> If the primary is "full_page_write = off", archive recovery may not act
>> > normally. Therefore the standby may need to check whether "full_page_write
>> > = off" to WAL.
>>
>> Isn't having a standby make the full_page_write = on in all case
>> (bypass configuration) ?
>
> what's the meaning?
Yeah. full_page_writes is a WAL generation parameter. Standbys don't
generate WAL. I think you just have to insist that the master has it
on.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2011-08-15 12:27:46 | Re: SSI error messages |
| Previous Message | Robert Haas | 2011-08-15 11:50:58 | Re: pg_stat_replication vs StandbyReplyMessage |