Re: Optimization for hot standby XLOG_STANDBY_LOCK redo

From: 邱宇航 <iamqyh(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Optimization for hot standby XLOG_STANDBY_LOCK redo
Date: 2020-05-06 03:05:06
Message-ID: 115D7093-4858-4B5D-8A3B-857DAB559159@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

And one more question, what LogAccessExclusiveLocks in LogStandbySnapshot is used for? Can We remove this.

> 2020年5月6日 上午10:36，邱宇航 <iamqyh(at)gmail(dot)com> 写道：
>
> I mean that all resources protected by XLOG_STANDBY_LOCK should redo later.
> The semantics of XLOG_STANDBY_LOCK is still kept.
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2020-05-06 04:40:54 Re: PG compilation error with Visual Studio 2015/2017/2019
Previous Message 邱宇航 2020-05-06 02:36:28 Re: Optimization for hot standby XLOG_STANDBY_LOCK redo