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

Re: pg_autovacuum does not start on system startup - 8.0 Release -

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Matthew T(dot) O'Connor" <matthew(at)tocr(dot)com>
Cc: "Harald Massa" <ghum(at)gmx(dot)net>,<pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: pg_autovacuum does not start on system startup - 8.0 Release -
Date: 2005-01-24 20:18:02
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E452863F@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-hackers-win32
 

> -----Original Message-----
> From: Matthew T. O'Connor [mailto:matthew(at)tocr(dot)com] 
> Sent: 24 January 2005 17:32
> To: Dave Page
> Cc: Harald Massa; pgsql-hackers-win32(at)postgresql(dot)org
> Subject: Re: [pgsql-hackers-win32] pg_autovacuum does not 
> start on system startup - 8.0 Release -
> 
> One answer might be to  have pg_autovacuum not be so 
> pessimistic failed 
> connections.  I wrote it so that pg_autovacuum exits if it fails to 
> connect.  Perhaps instead, when pg_autovacuum fails to 
> connect it should 
> sleep for a while and then retry.   Perhaps the best plan 
> would be a new 
> command line option that when used tells pg_autovacuum to continue to 
> retry for ever, when not used, it will still work the way it 
> always did.

Yeah, that's essentially what we're testing at the moment. If the
connection fails, it waits 30 seconds and trys again before bailing out
(though it only does it in Windows Service mode as the is the most
un-controllable startup type). It's a pretty un-invasive patch that
avoids adding command line options etc.

Regards, Dave.

pgsql-hackers-win32 by date

Next:From: Merlin MoncureDate: 2005-01-24 20:22:59
Subject: Re: long sql "in" clause crashes server process (8.0 Release)
Previous:From: Merlin MoncureDate: 2005-01-24 20:10:05
Subject: Re: long sql "in" clause crashes server process (8.0 Release)

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