Re: Remove a redundant condition check

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Ádám Balogh <adam(dot)balogh(at)ericsson(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Remove a redundant condition check
Date: 2020-06-26 09:09:22
Message-ID: CAA4eK1K3SFVroDr-vsy60coQ9v0+34MA0rxsn6G2j_EJvpf30A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 25, 2020 at 11:23 PM Ádám Balogh <adam(dot)balogh(at)ericsson(dot)com> wrote:
>
>
> A one line change to remove a duplicate check. This duplicate check was detected during testing my contribution to a static code analysis tool. There is no functional change, no new tests needed.
>
>

Yeah, this duplicate check is added as part of commit b2a5545bd6. See
below part of change.

- /*
- * If this record was a timeline switch, wake up any
- * walsenders to notice that we are on a new timeline.
- */
- if (switchedTLI && AllowCascadeReplication())
- WalSndWakeup();
+ /* Is this a timeline switch? */
+ if (switchedTLI)
+ {
+ /*
+ * Before we continue on the new timeline, clean up any
+ * (possibly bogus) future WAL segments on the old timeline.
+ */
+ RemoveNonParentXlogFiles(EndRecPtr, ThisTimeLineID);
+
+ /*
+ * Wake up any walsenders to notice that we are on a new
+ * timeline.
+ */
+ if (switchedTLI && AllowCascadeReplication())
+ WalSndWakeup();
+ }

It seems we forgot to remove the additional check for switchedTLI
while adding a new check. I think we can remove this duplicate check
in the HEAD code. I am not sure if it is worth to backpatch such a
change.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sébastien Lardière 2020-06-26 09:12:45 Re: PostgreSQL 13 Beta 1 Release Announcement Draft
Previous Message Magnus Hagander 2020-06-26 09:08:08 Re: Resetting spilled txn statistics in pg_stat_replication