Re: [PATCHES] Win32 pg_autovacuum service retry patch
[EMAIL PROTECTED] writes: > Anyway... the attached patch to pg_autovacuum follows Tom's earlier suggestion > that it re-try the inital database connection every 30 seconds for 5 minutes > before aborting when starting as a Windows Service. Applied. regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [PATCHES] Win32 pg_autovacuum service
> -Original Message- > From: Andrew Dunstan [mailto:[EMAIL PROTECTED] > Sent: 11 May 2004 12:13 > To: [EMAIL PROTECTED] > Subject: Re: [PATCHES] Win32 pg_autovacuum service > > I thought pg_autovacuum was moving to be integrated with and > controlled by the backend, in which case this seems > redundant, or have I become confused again? No, you haven't, but the last I remember was that it was no definite thing for 7.5, hence a win32 service might be useful for at least one release. Besides, I mainly did it as a learning exercise as I have to write a service at work - if it ends up in the bin I won't get upset :-) Regards, Dave. ---(end of broadcast)--- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [PATCHES] Win32 pg_autovacuum service
Dave Page said: > The attached patch allows pg_autovacuum to run as an application or a > service on Win32. There are minor changes that also affect *nix - > mainly: > > - The error logging function now takes an error level as an argument > for more consistent formatting and use in the windows event log. > - The default debug level is now 0 as 1 was creating a huge amount of > log output even on a small database. > - The main program loop has been moved into a separate function so it > can be called by the windows Service Control Manager. > I thought pg_autovacuum was moving to be integrated with and controlled by the backend, in which case this seems redundant, or have I become confused again? cheers andrew ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly