Re: pg_autovacuum Win32 service patch #2
От | Dave Page |
---|---|
Тема | Re: pg_autovacuum Win32 service patch #2 |
Дата | |
Msg-id | 03AF4E498C591348A42FC93DEA9661B889FD70@mail.vale-housing.co.uk обсуждение исходный текст |
Ответ на | pg_autovacuum Win32 service patch #2 ("Dave Page" <dpage@vale-housing.co.uk>) |
Список | pgsql-hackers |
> -----Original Message----- > From: Matthew T. O'Connor [mailto:matthew@zeut.net] > Sent: 13 May 2004 21:40 > To: Dave Page > Cc: pgsql-hackers-win32@postgresql.org; pgsql-hackers@postgresql.org > Subject: Re: [HACKERS] pg_autovacuum Win32 service patch #2 > > Anyway, not having looked at this at all, how will this be > effected when pg_autovacuum is integrated into the backend. > I assume that the postmaster can be run as a win32 service, > and if it launches and kills pg_autovacuum automatically, do > you need to do anything for pg_autovacuum? When it becomes part of the backend, the service code I've added will be junked. I've not looked at it in detail, but for the most part I imagine VacuumLoop() (which is where I moved the main loop to) will be tweaked and called from PostmasterMain (much as the stats collector is). Regards, Dave.
В списке pgsql-hackers по дате отправления: