RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly
Date
Msg-id OSCPR01MB14966C00587EEA20AA28718F1F57AA@OSCPR01MB14966.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-hackers
Dear Alexander,
> 
> Good idea.  But I think we should associate the "updated" flag
> directly to the fact that one slot (no matter logical or physical)
> changed its last_saved_restart_lsn.  See the attached patch.  I'm
> going to push it if no objections.

+        /*
+         * Track if we're going to update slot's last_saved_restart_lsn.
+         * We need this to know if we need to recompute the required LSN.
+         */
+        if (s->last_saved_restart_lsn != s->data.restart_lsn)
+            last_saved_restart_lsn_updated = true;

I feel no need to set to true if last_saved_restart_lsn_updated is already true.
Other than that it's OK for me.

Best regards,
Hayato Kuroda
FUJITSU LIMITED


pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Re: Virtual generated columns
Next
From: Ajit Awekar
Date:
Subject: Re: Unnecessary scan from non-overlapping range predicates