Commit2f1a78e

committed

Update item:

>> A more complex solution would be to save multiple plans for different> cardinality and use the appropriate plan based on the EXECUTE values.>

1 parent656beff commit2f1a78eCopy full SHA for 2f1a78e

File tree

-2

lines changed

-2

lines changed

Lines changed: 5 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -2,7 +2,7 @@`
`2`	`2`	`PostgreSQL TODO List`
`3`	`3`	`====================`
`4`	`4`	`Current maintainer:Bruce Momjian (pgman@candle.pha.pa.us)`
`5`		`-Last updated:Sat Dec17 14:03:20 EST 2005`
	`5`	`+Last updated:Thu Dec22 18:05:31 EST 2005`
`6`	`6`
`7`	`7`	`The most recent version of this document can be viewed at`
`8`	`8`	`http://www.postgresql.org/docs/faqs.TODO.html.`
`@@ -718,6 +718,10 @@ Dependency Checking`
`718`	`718`	`* Flush cached query plans when the dependent objects change,`
`719`	`719`	`when the cardinality of parameters changes dramatically, or`
`720`	`720`	`when new ANALYZE statistics are available`
	`721`	`+`
	`722`	`+ A more complex solution would be to save multiple plans for different`
	`723`	`+ cardinality and use the appropriate plan based on the EXECUTE values.`
	`724`	`+`
`721`	`725`	`* Track dependencies in function bodies and recompile/invalidate`
`722`	`726`
`723`	`727`	`This is particularly important for references to temporary tables`

Lines changed: 4 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -8,7 +8,7 @@`
`8`	`8`	`<bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF">`
`9`	`9`	`<h1><aname="section_1">PostgreSQL TODO List</a></h1>`
`10`	`10`	`<p>Current maintainer: Bruce Momjian (<ahref="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>`
`11`		`-Last updated:Sat Dec17 14:03:20 EST 2005`
	`11`	`+Last updated:Thu Dec22 18:05:31 EST 2005`
`12`	`12`	`</p>`
`13`	`13`	`<p>The most recent version of this document can be viewed at<br/>`
`14`	`14`	`<ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.`
`@@ -655,6 +655,9 @@ <h1><a name="section_11">Dependency Checking</a></h1>`
`655`	`655`	`<li>Flush cached query plans when the dependent objects change,`
`656`	`656`	`when the cardinality of parameters changes dramatically, or`
`657`	`657`	`when new ANALYZE statistics are available`
	`658`	`+<p> A more complex solution would be to save multiple plans for different`
	`659`	`+ cardinality and use the appropriate plan based on the EXECUTE values.`
	`660`	`+</p>`
`658`	`661`	`</li><li>Track dependencies in function bodies and recompile/invalidate`
`659`	`662`	`<p> This is particularly important for references to temporary tables`
`660`	`663`	`in PL/PgSQL because PL/PgSQL caches query plans. The only workaround`

Comments

(0)