From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
Cc: | <pgsql-hackers-win32(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] pg_autovacuum Win32 service patch #2 |
Date: | 2004-05-14 07:22:50 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B889FD70@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-hackers-win32 |
> -----Original Message-----
> From: Matthew T. O'Connor [mailto:matthew(at)zeut(dot)net]
> Sent: 13 May 2004 21:40
> To: Dave Page
> Cc: pgsql-hackers-win32(at)postgresql(dot)org; pgsql-hackers(at)postgresql(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Gaetano Mendola | 2004-05-14 09:33:15 | Re: pg_begintypend |
Previous Message | Greg Stark | 2004-05-14 05:17:30 | Re: PITR Dead horse? |
From | Date | Subject | |
---|---|---|---|
Next Message | pgsql | 2004-05-14 11:35:29 | Re: [pgsql-hackers-win32] Sync vs. fsync during |
Previous Message | Bruce Momjian | 2004-05-13 22:59:31 | Re: mingw configure failure detection |