| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Fix example plan in optimizer/README. |
| Date: | 2017-01-23 14:38:41 |
| Message-ID: | E1cVflZ-0008NW-Cj@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Fix example plan in optimizer/README.
Joining three tables only takes two join nodes. I think when I (tgl)
wrote this, I was envisioning possible additional joins; but since the
example doesn't show any fourth table, it's just confusing to write
a third join node.
Etsuro Fujita
Discussion: https://postgr.es/m/e6cfbaa3-af02-1abc-c25e-8fa5c6bc4e21@lab.ntt.co.jp
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/3c821466abcdb8120ab0dfbce02f3bbae3b62025
Modified Files
--------------
src/backend/optimizer/README | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-01-23 15:57:45 | pgsql: Prefetch blocks during lazy vacuum's truncation scan |
| Previous Message | Tom Lane | 2017-01-23 14:15:56 | pgsql: Volatile-ize some plperl variables that must survive into PG_CAT |