Re: Possible documentation inaccuracy in optimizer README

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Zeyuan Hu <ferrishu3886(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org
Subject: Re: Possible documentation inaccuracy in optimizer README
Date: 2025-04-09 02:36:57
Message-ID: CAApHDvoxSLCeQ=m35Je9L7VM_2cGKvxvRPwK0vihQzSyKzsJFA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Wed, 9 Apr 2025 at 14:33, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.)

Looks good to me.

David

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Tom Lane 2025-04-09 03:04:54 Re: Possible documentation inaccuracy in optimizer README
Previous Message Tom Lane 2025-04-09 02:33:52 Re: Possible documentation inaccuracy in optimizer README