public inbox for [email protected]
help / color / mirror / Atom feedFrom: Abhi Kaki <[email protected]>
To: [email protected]
Subject: Typo Fixes and Patch
Date: Wed, 15 Apr 2026 17:22:07 -0700
Message-ID: <CA+FnxSJTDnU4=EX+ZC2=m6tpgdVPo_HCPFUmZ9Wkrq+UP=Tu8g@mail.gmail.com> (raw)
Hi Hackers,
Fixed a couple of typo errors in the graph table and attached a patch.
Please review.
Regards,
Abhi
Attachments:
[application/octet-stream] fix_typos_pgpa.patch (1.5K, 3-fix_typos_pgpa.patch)
download | inline diff:
diff --git a/contrib/pg_plan_advice/pgpa_join.c b/contrib/pg_plan_advice/pgpa_join.c
index 38e7b91ed7e..067321081e7 100644
--- a/contrib/pg_plan_advice/pgpa_join.c
+++ b/contrib/pg_plan_advice/pgpa_join.c
@@ -93,7 +93,7 @@ pgpa_create_join_unroller(void)
*
* pgpa_plan_walker creates a "top level" join unroller object when it
* encounters a join in a portion of the plan tree in which no join unroller
- * is already active. From there, this function is responsible for determing
+ * is already active. From there, this function is responsible for determining
* to what portion of the plan tree that join unroller applies, and for
* creating any subordinate join unroller objects that are needed as a result
* of non-outer-deep join trees. We do this by returning the join unroller
diff --git a/contrib/pg_plan_advice/pgpa_output.c b/contrib/pg_plan_advice/pgpa_output.c
index ed5a9340671..dd3ba692a86 100644
--- a/contrib/pg_plan_advice/pgpa_output.c
+++ b/contrib/pg_plan_advice/pgpa_output.c
@@ -114,7 +114,7 @@ pgpa_output_advice(StringInfo buf, pgpa_plan_walker_context *walker,
context.wrap_column = 76;
/*
- * Each piece of JOIN_ORDER() advice fully describes the join order for a
+ * Each piece of JOIN_ORDER() advice fully describes the join order for
* a single unrolled join. Merging is not permitted, because that would
* change the meaning, e.g. SEQ_SCAN(a b c d) means simply that sequential
* scans should be used for all of those relations, and is thus equivalent
view thread (3+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Typo Fixes and Patch
In-Reply-To: <CA+FnxSJTDnU4=EX+ZC2=m6tpgdVPo_HCPFUmZ9Wkrq+UP=Tu8g@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox