Improve wording in a few comments
authorDavid Rowley <drowley@postgresql.org>
Fri, 19 Sep 2025 11:35:53 +0000 (23:35 +1200)
committerDavid Rowley <drowley@postgresql.org>
Fri, 19 Sep 2025 11:35:53 +0000 (23:35 +1200)
commit6fa2688a9d63c190da0f19eb61a23b72eea110a2
treeed8a7cb7bce9db1a6ca806931d8e3bafe37d3ac3
parent9a82a64edcd8615cf16eae64bf1572d4156cb912
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@gmail.com>
Discussion: https://postgr.es/m/CAHewXNmSYWPud1sfBvpKbCJeRkWeZYuqatxtV9U9LvAFXBEiBw@mail.gmail.com
Backpatch-through: 18
src/backend/optimizer/path/indxpath.c