Re: Autovacuum in the backend

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Magnus Hagander" <mha(at)sollentuna(dot)net>, "Josh Berkus" <josh(at)agliodbs(dot)com>, "Gavin Sherry" <swm(at)linuxworld(dot)com(dot)au>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Autovacuum in the backend
Date: 2005-06-16 10:42:40
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E490E535@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Magnus Hagander [mailto:mha(at)sollentuna(dot)net]
> Sent: 16 June 2005 10:15
> To: Josh Berkus; Gavin Sherry
> Cc: Bruce Momjian; pgsql-hackers(at)postgresql(dot)org; Dave Page
> Subject: RE: [HACKERS] Autovacuum in the backend
>
> > If we do integrated AV, it should only be turned on by
> > default at a relatively low level. And wasn't there an issue
> > on Windows with AV not working?
>
> AFAIK, it works.
> But the fact that you need to provide it with a userid/password combo
> makes it a lot harder to install as a service. And it's not
> installed by
> default by the installer, for that reason (and I think maybe others?
> Dave, I think you're the one who said no-service-by-default?)

Yes, 'cos there was no easy way to do it securely when I did it without
a lot of mucking about to setup a .pgpass file in the service users
account.

It does work perfectly well however, and did so long before PostgreSQL
itself did :-)

Regards, Dave

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2005-06-16 10:55:40 Re: Autovacuum in the backend
Previous Message Simon Riggs 2005-06-16 10:22:21 Re: [HACKERS] INHERITS and planning