| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| 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:33:52 |
| Message-ID: | 111828.1744166032@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
David Rowley <dgrowleyml(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2025-04-09 02:36:57 | Re: Possible documentation inaccuracy in optimizer README |
| Previous Message | David Rowley | 2025-04-09 01:24:29 | Re: Possible documentation inaccuracy in optimizer README |