NotificationsYou must be signed in to change notification settings
Fork6
Star31

Commit3c82146

committed

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 theexample doesn't show any fourth table, it's just confusing to writea third join node.Etsuro FujitaDiscussion:https://postgr.es/m/e6cfbaa3-af02-1abc-c25e-8fa5c6bc4e21@lab.ntt.co.jp

1 parentc0ef456 commit3c82146Copy full SHA for 3c82146

File tree

1 file changed

-3

lines changed

src/backend/optimizer
- README

1 file changed

-3

lines changed

`‎src/backend/optimizer/README`

Lines changed: 2 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -757,9 +757,8 @@ to create a plan like`
`757`	`757`	`-> Seq Scan on SmallTable1 A`
`758`	`758`	`NestLoop`
`759`	`759`	`-> Seq Scan on SmallTable2 B`
`760`		`- NestLoop`
`761`		`- -> Index Scan using XYIndex on LargeTable C`
`762`		`- Index Condition: C.X = A.AID and C.Y = B.BID`
	`760`	`+ -> Index Scan using XYIndex on LargeTable C`
	`761`	`+ Index Condition: C.X = A.AID and C.Y = B.BID`
`763`	`762`
`764`	`763`	`so we should be willing to pass down A.AID through a join even though`
`765`	`764`	`there is no join order constraint forcing the plan to look like this.`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit3c82146

File tree

1 file changed

1 file changed

`‎src/backend/optimizer/README`

0 commit comments