Re: [PROPOSAL] VACUUM Progress Checker.
| От | Robert Haas |
|---|---|
| Тема | Re: [PROPOSAL] VACUUM Progress Checker. |
| Дата | |
| Msg-id | CA+TgmoZHb6n6WRDMjTXusp_fAptsx5Dyj0nuSr7XfK-xV+RAeA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [PROPOSAL] VACUUM Progress Checker. (Jim Nasby <Jim.Nasby@BlueTreble.com>) |
| Список | pgsql-hackers |
On Fri, Jul 24, 2015 at 2:00 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote: >> 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. > > I was thinking your DSM stuff would come into play here. We wouldn't want to > be reallocating during execution, but I'd expect we would know during setup > how much memory we actually needed. You could make that work, but it would be a pretty significant amount of new mechanism. Also, if it's to be practical to report progress frequently, it's got to be cheap, and that precludes reporting vast volumes of data. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: