Re: Possible documentation inaccuracy in optimizer README - Mailing list pgsql-docs

From Tom Lane
Subject Re: Possible documentation inaccuracy in optimizer README
Date
Msg-id 3887651.1744086487@sss.pgh.pa.us
Whole thread Raw
In response to Possible documentation inaccuracy in optimizer README  (Zeyuan Hu <ferrishu3886@gmail.com>)
Responses Re: Possible documentation inaccuracy in optimizer README
Re: Possible documentation inaccuracy in optimizer README
List pgsql-docs
Zeyuan Hu <ferrishu3886@gmail.com> writes:
> In https://github.com/postgres/postgres/tree/master/src/backend/optimizer,
> there are two examples on the dynamic programming (DP) algorithm used in
> the optimizer, which I think
> have some inaccuracy:

You're right that these examples do not consider the effects of
clauses generated by the EquivalenceClass machinery.  But I don't
think the exposition would be improved by mentioning that here.
The point of these examples is that we don't consider joining
rels that have no linking clauses at all.

We could possibly avoid the inaccuracy by making the examples use
some other operators that are not equijoins.  But I wonder if that
would not be more confusing rather than less so.

            regards, tom lane



pgsql-docs by date:

Previous
From: Zeyuan Hu
Date:
Subject: Possible documentation inaccuracy in optimizer README
Next
From: Yaroslav Saburov
Date:
Subject: Re: generated constraint name