Re: [PROPOSAL] VACUUM Progress Checker.

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: [PROPOSAL] VACUUM Progress Checker.
Дата
Msg-id CA+Tgmob9e4izmGBxJsBMLePCuMFUbLi6WOQAShfUaxm08e_b9w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [PROPOSAL] VACUUM Progress Checker.  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Ответы Re: [PROPOSAL] VACUUM Progress Checker.  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Список pgsql-hackers
On Wed, Jul 22, 2015 at 11:28 AM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
> If we want to expose that level of detail, I think either JSON or arrays
> would make more sense, so we're not stuck with a limited amount of info.
> Perhaps DDL would be OK with the numbers you suggested, but
> https://www.pgcon.org/2013/schedule/events/576.en.html would not, and I
> think wanting query progress is much more common.

You need to restrict the amount of info, because you've got to
preallocate enough shared memory to store all the data that somebody
might report.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: What is HeapScanDescData.rs_initblock good for?
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: Restore-reliability mode