On Thu, 2007-01-11 at 16:11 -0500, Tom Lane wrote: > "Simon Riggs" <simon@xxxxxxxxxxxxxxx> writes: > > It's not clear to me how this fix will alter the INSERT issue Kim > > mentions. > > I didn't say that it would; we have no information on the INSERT issue, > so I'm just concentrating on the problem that he did provide info on. OK. > I'm frankly not real surprised that there are performance issues with > such a huge pg_class; it's not a regime that anyone's spent any time > optimizing. Yeh, I saw a pg_class that big once, but it just needed a VACUUM. Temp relations still make pg_class entried don't they? Is that on the TODO list to change? -- Simon Riggs EnterpriseDB http://www.enterprisedb.com
