pgsql: Rename variable for code clarity - Mailing list pgsql-committers

From Daniel Gustafsson
Subject pgsql: Rename variable for code clarity
Date
Msg-id E1qhCK9-0040gj-8w@gemulon.postgresql.org
Whole thread Raw
List 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@gmail.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(-)


pgsql-committers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: pgsql: Remove unnecessary smgrimmedsync() when creating unlogged table.
Next
From: Tom Lane
Date:
Subject: pgsql: Fix get_expr_result_type() to find field names for RECORD Consts