Re: Plan time Improvement - 64bit bitmapset
От | Gregory Stark |
---|---|
Тема | Re: Plan time Improvement - 64bit bitmapset |
Дата | |
Msg-id | 87ljo987ri.fsf@oxford.xeocode.com обсуждение исходный текст |
Ответ на | Re: Plan time Improvement - 64bit bitmapset ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
Ответы |
Re: Plan time Improvement - 64bit bitmapset
Re: Plan time Improvement - 64bit bitmapset |
Список | pgsql-hackers |
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes: > Andres Freund <andres@anarazel.de> wrote: > >> long plan times (minutes and up) > > Wow. I thought I had some pretty complex queries, including some > which join using several views, each of which has several joins; but > I've never gone to multiple seconds on plan time (much less multiple > minutes!) without very high statistics targets and many indexes on the > tables. Any rough estimates on those? My money's still on very large statistics targets. If you have a lot of columns and 1,000-element arrays for each column that can get big pretty quickly. But that doesn't explain the bitmap ops being important. Hm. Actually having a lot of columns and then joining a lot of tables could mean having fairly large bitmapsets. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support!
В списке pgsql-hackers по дате отправления: