Re: pg_autovacuum fails to start - 8.0 Release

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Harald Massa" <ghum(at)gmx(dot)net>
Cc: <pgsql-hackers-win32(at)postgresql(dot)org>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: pg_autovacuum fails to start - 8.0 Release
Date: 2005-01-20 16:23:47
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4528586@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers-win32 pgsql-patches

> -----Original Message-----
> From: Harald Massa [mailto:ghum(at)gmx(dot)net]
> Sent: 20 January 2005 16:17
> To: Dave Page
> Cc: pgsql-hackers-win32(at)postgresql(dot)org; pgsql-patches(at)postgresql(dot)org
> Subject: RE: [pgsql-hackers-win32] pg_autovacuum fails to
> start - 8.0 Release
>
> Dave,
>
> > You probably need to restart after editting it so that the
> SCM reloads
> > it.
>
> I am not quite sure if that really helped. Either way, I
> found a workaround
> and want to have it within googling space:
>
> at the moment the rest of the command-line after -E is stored
> within the
> DependOnService Property.
>
> So the easiest fix is to have -E as the last parameter when
> creating the
> pg_autovacuum service...
>
> that creates an
> DependOnService pgsql-8.0
> Key-Entry within the registry and it works ....

Not every time unfortunately. It very much depends on the state of the
memory and whether or not you end up with an extra null on the end of
the string. In testing I found that often didn't happen.

Regards, Dave

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message Dave Page 2005-01-21 09:39:13 Re: [PATCHES] pg_autovacuum fails to start - 8.0 Release
Previous Message Harald Massa 2005-01-20 16:16:50 Re: pg_autovacuum fails to start - 8.0 Release

Browse pgsql-patches by date

  From Date Subject
Next Message Neil Conway 2005-01-21 01:09:20 regression: pass with no default WITH OIDS
Previous Message Harald Massa 2005-01-20 16:16:50 Re: pg_autovacuum fails to start - 8.0 Release