pgsql: Rename variable for code clarity

From: Daniel Gustafsson <dgustafsson(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Rename variable for code clarity
Date: 2023-09-15 17:09:45
Message-ID: E1qhCK9-0040gj-8w@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Rename variable for code clarity

When tracking IO timing for WAL, the duration is what we calculate
based on the start and end timestamps, it's not what the variable
contains. Rename the timestamp variable to end to better communicate
what it contains. Original patch by Krishnakumar with additional
hacking to fix another occurrence by me.

Author: Krishnakumar R <kksrcv001(at)gmail(dot)com>
Discussion: https://postgr.es/m/CAPMWgZ9f9o8awrQpjo8oxnNQ=bMDVPx00NE0QcDzvHD_ZrdLPw@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/a396e20ad0da42b9cf64c39a99034523d819f008

Modified Files
--------------
src/backend/access/transam/xlog.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2023-09-15 21:02:06 pgsql: Track nesting depth correctly when drilling down into RECORD Var
Previous Message Heikki Linnakangas 2023-09-15 14:53:25 pgsql: Remove unnecessary smgrimmedsync() when creating unlogged table.