> > 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.
> 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?
Yeah, I meant that when writing "configurable" ... that is ment to be a
command line parameter. So maybe the default should be 0 to 3 seconds.
(and the command line switch should expect seconds)
In response to
pgsql-hackers-win32 by date
|Next:||From: Matthew T. O'Connor||Date: 2005-01-24 17:31:37|
|Subject: Re: pg_autovacuum does not start on system|
|Previous:||From: Harald Massa||Date: 2005-01-24 10:58:33|
|Subject: long sql "in" clause crashes server process (8.0 Release)|