Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] pg_autovacuum Win32 service patch #2

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-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.

pgsql-hackers by date

Next:From: Gaetano MendolaDate: 2004-05-14 09:33:15
Subject: Re: pg_begintypend
Previous:From: Greg StarkDate: 2004-05-14 05:17:30
Subject: Re: PITR Dead horse?

pgsql-hackers-win32 by date

Next:From: pgsqlDate: 2004-05-14 11:35:29
Subject: Re: [pgsql-hackers-win32] Sync vs. fsync during
Previous:From: Bruce MomjianDate: 2004-05-13 22:59:31
Subject: Re: mingw configure failure detection

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group