Commit3531383

committed

Just noticed that you can't Query-Cancel a long planner run, because

no part of the planner did CHECK_FOR_INTERRUPTS(). Add one in asuitably strategic spot.

1 parent1bdec34 commit3531383Copy full SHA for 3531383

File tree

-1

lines changed

-1

lines changed

Lines changed: 7 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -8,7 +8,7 @@`
`8`	`8`	`*`
`9`	`9`	`*`
`10`	`10`	`* IDENTIFICATION`
`11`		`- * $PostgreSQL: pgsql/src/backend/optimizer/util/pathnode.c,v 1.120 2005/04/25 01:30:13 tgl Exp $`
	`11`	`+ * $PostgreSQL: pgsql/src/backend/optimizer/util/pathnode.c,v 1.121 2005/06/03 19:00:12 tgl Exp $`
`12`	`12`	`*`
`13`	`13`	`*-------------------------------------------------------------------------`
`14`	`14`	`*/`
`@@ -277,6 +277,12 @@ add_path(RelOptInfo parent_rel, Path new_path)`
`277`	`277`	`ListCell*p1_prev=NULL;`
`278`	`278`	`ListCell*p1;`
`279`	`279`
	`280`	`+/*`
	`281`	`+ * This is a convenient place to check for query cancel --- no part`
	`282`	`+ * of the planner goes very long without calling add_path().`
	`283`	`+ */`
	`284`	`+CHECK_FOR_INTERRUPTS();`
	`285`	`+`
`280`	`286`	`/*`
`281`	`287`	`* Loop to check proposed new path against old paths. Note it is`
`282`	`288`	`* possible for more than one old path to be tossed out because`

Comments

(0)