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 111828.1744166032@sss.pgh.pa.us
Whole thread Raw
In response to Re: Possible documentation inaccuracy in optimizer README  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: Possible documentation inaccuracy in optimizer README
List pgsql-docs
David Rowley <dgrowleyml@gmail.com> writes:
> I don't think it'd hurt to mention that we're just ignoring the
> existence of ECs for this example.

Seems like a reasonable approach.

> -    (other possibilities will be excluded for lack of join clauses)
> +    (other possibilities will be excluded for lack of join clauses
> +    (technically, EquivalenceClasses do allow us to determine derived join
> +    clauses for this case, but we ignore that for the simplicity of this
> +    example))

Maybe better:

    Other possibilities will be excluded for lack of join clauses.
    (In reality, use of EquivalenceClasses would allow us to
    deduce additional join clauses that allow more join
    combinations, but here we ignore that to preserve the
    simplicity of this example.)

            regards, tom lane



pgsql-docs by date:

Previous
From: David Rowley
Date:
Subject: Re: Possible documentation inaccuracy in optimizer README
Next
From: David Rowley
Date:
Subject: Re: Possible documentation inaccuracy in optimizer README