Re: switch UNLOGGED to LOGGED - Mailing list pgsql-hackers

From Robert Haas
Subject Re: switch UNLOGGED to LOGGED
Date
Msg-id BANLkTi=d+M8bxzxq0UNa+Cr_mO4uD4DigQ@mail.gmail.com
Whole thread Raw
In response to Re: switch UNLOGGED to LOGGED  (Noah Misch <noah@leadboat.com>)
Responses Re: switch UNLOGGED to LOGGED  (Noah Misch <noah@leadboat.com>)
Re: switch UNLOGGED to LOGGED  (Leonardo Francalanci <m_lists@yahoo.it>)
List pgsql-hackers
On Fri, May 27, 2011 at 6:19 AM, Noah Misch <noah@leadboat.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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: How can I check the treatment of bug fixes?
Next
From: Josh Kupershmidt
Date:
Subject: psql: missing tab completions for COMMENT ON