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

Re: pg_autovacuum Win32 Service startup delay

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-patches(at)postgresql(dot)org>
Subject: Re: pg_autovacuum Win32 Service startup delay
Date: 2005-01-25 12:39:35
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4528660@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-patches
 

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us] 
> Sent: 24 January 2005 23:58
> To: Dave Page
> Cc: pgsql-patches(at)postgresql(dot)org
> Subject: Re: [PATCHES] pg_autovacuum Win32 Service startup delay 
> 
> "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
> > When starting as a service at boot time on Windows, 
> pg_autovacuum may
> > fail to start because the PostgreSQL service is still 
> starting up. This
> > patch causes the service to attempt a second connection 30 
> seconds after
> > the initial connection failure before giving up entirely.
> 
> Hm.  In event that the system crashed beforehand, it could 
> require much
> more than 30 seconds to finish replaying the old WAL log.  So 
> the above
> doesn't seem super robust to me.  Would it be reasonable to 
> try every 30
> seconds for five minutes, or some such?  (Five minutes at least has a
> defensible rationale, ie it's the default checkpoint interval and we
> expect we can replay the log at least as fast as it was created
> initially.)

OK, revised patch attached. This version tries every 30 seconds for 5
minutes then gives up.

Regards, Dave.

Attachment: startup_delay.diff
Description: application/octet-stream (1.4 KB)

pgsql-patches by date

Next:From: Mahmoud TaghizadehDate: 2005-01-25 13:35:43
Subject: add collation support to postgresql
Previous:From: Christopher BrowneDate: 2005-01-25 12:03:28
Subject: Re: Much Ado About COUNT(*)

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