Merlin Moncure <mmoncure@xxxxxxxxx> writes: > On Thu, Apr 16, 2009 at 8:05 AM, Matthew Wakeling <matthew@xxxxxxxxxxx> wrote: >> That solves the problem. So, a view is treated as a subquery then? > no...the view is simply inlined into the query (think C macro) using > the rules. You just bumped into an arbitrary (and probably too low) > limit into the number of tables the planner can look at in terms of > optimizing certain types of plans. Bear in mind that those limits exist to keep you from running into exponentially increasing planning time when the size of a planning problem gets big. "Raise 'em to the moon" isn't really a sane strategy. It might be that we could get away with raising them by one or two given the general improvement in hardware since the values were last looked at; but I'd be hesitant to push the defaults further than that. regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
