Re: ANALYZE command progress checker
От | Robert Haas |
---|---|
Тема | Re: ANALYZE command progress checker |
Дата | |
Msg-id | CA+TgmoYoK59_DRsLYwkL8UeX4_jL3ejWG0ruvgqWFF-a0=_8VA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: ANALYZE command progress checker (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>) |
Список | pgsql-hackers |
On Tue, Apr 4, 2017 at 4:57 AM, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> wrote: > Hmm, you're right. It could be counted with a separate variable > initialized to 0 and incremented every time we decide to add a row to the > final set of sampled rows, although different implementations of > AcquireSampleRowsFunc have different ways of deciding if a given row will > be part of the final set of sampled rows. > > On the other hand, if we decide to count progress in terms of blocks as > you suggested afraid, I'm afraid that FDWs won't be able to report the > progress. I think it may be time to push this patch out to v11. It was submitted one day before the start of the last CommitFest, the design wasn't really right, and it's not clear even now that we know what the right design is. And we're pretty much out of time. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: