| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Leonardo Francalanci <m_lists(at)yahoo(dot)it>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: switch UNLOGGED to LOGGED |
| Date: | 2011-05-29 01:33:09 |
| Message-ID: | BANLkTi=d+M8bxzxq0UNa+Cr_mO4uD4DigQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 27, 2011 at 6:19 AM, Noah Misch <noah(at)leadboat(dot)com> wrote:
>> So, it's ok to have a log item that is replayed only if
>>
>> WalRcvInProgress()
>>
>> is true?
>
> No, that checks for WAL streaming in particular. A log-shipping standby needs
> the same treatment.
>
>> Is it a correct approach? I couldn't find any other way to
>> find out if we are in a standby or a master...
>
> InArchiveRecovery looks like the right thing, but it's currently static to
> xlog.c. Perhaps exporting that is the way to go.
Why is it necessary to replay the operation only on the slave? Can we
just use XLOG_HEAP_NEWPAGE?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2011-05-29 02:01:11 | Re: How can I check the treatment of bug fixes? |
| Previous Message | Robert Haas | 2011-05-29 01:31:06 | Re: How can I check the treatment of bug fixes? |