From: | "Harald Massa" <ghum(at)gmx(dot)net> |
---|---|
To: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | pgsql-hackers-win32(at)postgresql(dot)org |
Subject: | Re: pg_autovacuum does not start on system startup - 8.0 Release - |
Date: | 2005-01-24 11:02:10 |
Message-ID: | 13916.1106564530@www5.gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers-win32 |
Dave,
> > 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)
Harald
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew T. O'Connor | 2005-01-24 17:31:37 | Re: pg_autovacuum does not start on system |
Previous Message | Harald Massa | 2005-01-24 10:58:33 | long sql "in" clause crashes server process (8.0 Release) |