On Wed, May 6, 2020 at 8:35 AM 邱宇航 wrote:
>
> And one more question, what LogAccessExclusiveLocks in LogStandbySnapshot is
> used for?
>
As far as I understand, this is required to ensure that we have
acquired all the AccessExclusiveLocks on relations before we can say
standby has reached STANDB
And one more question, what LogAccessExclusiveLocks in LogStandbySnapshot is
used for? Can We remove this.
> 2020年5月6日 上午10:36，邱宇航 写道：
>
> I mean that all resources protected by XLOG_STANDBY_LOCK should redo later.
> The semantics of XLOG_STANDBY_LOCK is still kept.
>
I mean that all resources protected by XLOG_STANDBY_LOCK should redo later.
The semantics of XLOG_STANDBY_LOCK is still kept.
> 2020年4月30日 下午7:12，Amit Kapila 写道：
>
> On Thu, Apr 30, 2020 at 4:07 PM 邱宇航 wrote:
>>
>> I noticed that in hot standby, XLOG_STANDBY_LOCK redo is sometimes block by
>>
On Thu, Apr 30, 2020 at 4:07 PM 邱宇航 wrote:
>
> I noticed that in hot standby, XLOG_STANDBY_LOCK redo is sometimes block by
> another query, and all the rest redo is blocked by this lock getting
> operation, which is not good and often happed in my database, so the hot
> standby will be left beh
I noticed that in hot standby, XLOG_STANDBY_LOCK redo is sometimes block by
another query, and all the rest redo is blocked by this lock getting operation,
which is not good and often happed in my database, so the hot standby will be
left behind and master will store a lot of WAL which can’t be
