Re: Optimizer docs typos

From: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Optimizer docs typos
Date: 2020-05-19 10:35:56
Message-ID: CAPmGK16RM-LBWqA31O6ixfgUCmFkTZc7wRt_0WPp3VNf+_7D9w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 18, 2020 at 7:45 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> In this same README doc, another suspicious typo to me, which happens in
> section "Optimizer Functions", is in the prefix to query_planner(),
> we should have three dashes, rather than two, since query_planner() is
> called within grouping_planner().
>
> diff --git a/src/backend/optimizer/README b/src/backend/optimizer/README
> index 7dcab9a..bace081 100644
> --- a/src/backend/optimizer/README
> +++ b/src/backend/optimizer/README
> @@ -315,7 +315,7 @@ set up for recursive handling of subqueries
> preprocess target list for non-SELECT queries
> handle UNION/INTERSECT/EXCEPT, GROUP BY, HAVING, aggregates,
> ORDER BY, DISTINCT, LIMIT
> ---query_planner()
> +---query_planner()
> make list of base relations used in query
> split up the qual into restrictions (a=1) and joins (b=c)
> find qual clauses that enable merge and hash joins

Yeah, you are right. Another one would be in the prefix to
standard_join_search(); I think it might be better to have six dashes,
rather than five, because standard_join_search() is called within
make_rel_from_joinlist().

Best regards,
Etsuro Fujita

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2020-05-19 11:02:12 Re: Expand the use of check_canonical_path() for more GUCs
Previous Message Dilip Kumar 2020-05-19 10:00:55 Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions