Re: pg_autovacuum does not start on system startup - 8.0 Release - - Mailing list pgsql-hackers-win32

From Dave Page
Subject Re: pg_autovacuum does not start on system startup - 8.0 Release -
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E45285F0@ratbert.vale-housing.co.uk
Whole thread Raw
Responses Re: pg_autovacuum does not start on system  ("Matthew T. O'Connor" <matthew@tocr.com>)
List pgsql-hackers-win32

> -----Original Message-----
> From: Harald Massa [mailto:ghum@gmx.net]
> Sent: 24 January 2005 10:45
> To: Dave Page
> Cc: pgsql-hackers-win32@postgresql.org
> Subject: Re: [pgsql-hackers-win32] pg_autovacuum does not
> start on system startup - 8.0 Release -
>
> Dave,
>
> > > As said... I can start that service manually after Windows
> > > starts talking to
> > > me. What can I do to make it run properly?
> >
> > Hmm, I'll have to think about the best way to do that.
>
> My impression is that Service-startup is rather
> nondeterministic in aspects
> of timing.
>
> So I would suggest to integrate that sleepy workaround within
> pg_autovacuum
> service. Just let it sleep for 'some time' ... maybe even
> configurable ...
> before it connects. (recommended default: 180 seconds; NOT
> microseconds and
> NOT milliseconds :))

Uh-huh :-)

The problem with that is that with service start taking 3 minutes,
restarting the service manually could be somewhat annoying for simple
config changes (bear in mind that the service doesn't report that it is
running until it has connected successfully to the database). What about
a command line option to specify a delay? That way the user will know
about it because they will have specified it?

Regards, Dave.

pgsql-hackers-win32 by date:

Previous
From: "Harald Massa"
Date:
Subject: Re: pg_autovacuum does not start on system startup - 8.0 Release -
Next
From: "Harald Massa"
Date:
Subject: long sql "in" clause crashes server process (8.0 Release)