pgsql: Improve wording in a few comments

From: David Rowley <drowley(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Improve wording in a few comments
Date: 2025-09-19 11:35:43
Message-ID: E1uzZOx-001Tie-09@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Improve wording in a few comments

Initially this was to fix the "catched" typo, but I (David) wasn't quite
clear on what the previous comment meant about being "effective". I
expect this means efficiency, so I've reworded the comment to indicate
that.

While this is only a comment fixup, for the sake of possibly minimizing
possible future backpatching pain, I've opted to backpatch to 18 since
this code is new to that version and the release isn't out the door yet.

Author: Tender Wang <tndrwang(at)gmail(dot)com>
Discussion: https://postgr.es/m/CAHewXNmSYWPud1sfBvpKbCJeRkWeZYuqatxtV9U9LvAFXBEiBw@mail.gmail.com
Backpatch-through: 18

Branch
------
master

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

Modified Files
--------------
src/backend/optimizer/path/indxpath.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message David Rowley 2025-09-19 11:36:10 pgsql: Improve wording in a few comments
Previous Message Amit Kapila 2025-09-19 05:48:41 pgsql: Add optional pid parameter to pg_replication_origin_session_setu