Re: Is Recovery actually paused? - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Re: Is Recovery actually paused?
Date
Msg-id CALj2ACVi4o9z4NjWZS8QeVbLFdstWMh+ebpMZkfQq0=2Z099iQ@mail.gmail.com
Whole thread Raw
In response to Re: Is Recovery actually paused?  (Dilip Kumar <dilipbalaut@gmail.com>)
Responses Re: Is Recovery actually paused?  (Dilip Kumar <dilipbalaut@gmail.com>)
List pgsql-hackers
On Thu, Feb 4, 2021 at 7:20 PM Dilip Kumar <dilipbalaut@gmail.com> wrote:
> > How can we do that this is not a 1 byte flag this is enum so I don't
> > think we can read any atomic state without a spin lock here.
>
> I have fixed the other comments and the updated patch is attached.

Can we just do like below so that we could use the existing
SetRecoveryPause instead of setting the state outside?

    /* loop until recoveryPauseState is set to RECOVERY_NOT_PAUSED */
    while (1)
    {
        RecoveryPauseState state;

        state = GetRecoveryPauseState();

        if (state == RECOVERY_NOT_PAUSED)
            break;

        HandleStartupProcInterrupts();

        if (CheckForStandbyTrigger())
            return;
        pgstat_report_wait_start(WAIT_EVENT_RECOVERY_PAUSE);

        /*
         * If recovery pause is requested then set it paused.  While we are in
         * the loop, user might resume and pause again so set this every time.
         */
        if (state == RECOVERY_PAUSE_REQUESTED)
            SetRecoveryPause(RECOVERY_PAUSED)

And a typo - it's "pg_is_wal_replay_paused" not
"pg_is_wal_repay_paused" +
<function>pg_is_wal_repay_paused()</function> returns whether a
request

With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Zhihong Yu
Date:
Subject: Re: [HACKERS] GSoC 2017: Foreign Key Arrays
Next
From: Peter Smith
Date:
Subject: Re: Single transaction in the tablesync worker?