On Tue, Oct 17, 2017 at 7:53 AM, Michael Paquier
wrote:
> On Mon, Oct 16, 2017 at 9:50 PM, Amit Kapila wrote:
>> If above analysis is correct, then I think we can say that row state
>> in a page will be same during recovery as it was when the original
>> operation was performed if the full_page_w
On Mon, Oct 16, 2017 at 9:50 PM, Amit Kapila wrote:
> If above analysis is correct, then I think we can say that row state
> in a page will be same during recovery as it was when the original
> operation was performed if the full_page_writes are enabled. I am not
> sure how much this can help in c
On Fri, Oct 13, 2017 at 11:57 AM, Amit Kapila wrote:
> On Fri, Oct 13, 2017 at 10:32 AM, Michael Paquier
> wrote:
>> On Thu, Oct 12, 2017 at 10:47 PM, Amit Kapila
>> wrote:
>>> Today, I was trying to think about cases when we can return BLK_DONE
>>> in XLogReadBufferForRedoExtended. One thing
On Fri, Oct 13, 2017 at 10:32 AM, Michael Paquier
wrote:
> On Thu, Oct 12, 2017 at 10:47 PM, Amit Kapila wrote:
>> Today, I was trying to think about cases when we can return BLK_DONE
>> in XLogReadBufferForRedoExtended. One thing that occurred to me is
>> that it can happen during the replay of
On Thu, Oct 12, 2017 at 10:47 PM, Amit Kapila wrote:
> Today, I was trying to think about cases when we can return BLK_DONE
> in XLogReadBufferForRedoExtended. One thing that occurred to me is
> that it can happen during the replay of WAL if the full_page_writes is
> off. Basically, when the ful
Today, I was trying to think about cases when we can return BLK_DONE
in XLogReadBufferForRedoExtended. One thing that occurred to me is
that it can happen during the replay of WAL if the full_page_writes is
off. Basically, when the full_page_writes is on, then during crash
recovery, it will alway
