Re: Utility database (Was: RE: Autovacuum in the backend)

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
Cc: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>, "Magnus Hagander" <mha(at)sollentuna(dot)net>, "Josh Berkus" <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Utility database (Was: RE: Autovacuum in the backend)
Date: 2005-06-17 19:40:56
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E490E591@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: 17 June 2005 15:09
> To: Christopher Kings-Lynne
> Cc: Andreas Pflug; Magnus Hagander; Dave Page; Josh Berkus;
> pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] Utility database (Was: RE: Autovacuum
> in the backend)
>
> One argument against this is that it'd mean another copy of the system
> catalogs in a standard installation. That's been running
> three to five
> megabytes over the last few releases. Disk space is pretty
> cheap these
> days, but we do get occasional complaints from people who wish the
> footprint was smaller.

Yeah, but those people could easily drop it to save that space. They'd
have to offer an alternative default db for their users, but then I
guess they probably have pretty unusual requirements anyway so I doubt
that would add any pain.

Regards, Dave.

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2005-06-17 19:56:15 Re: Utility database (Was: RE: Autovacuum in the backend)
Previous Message Bruce Momjian 2005-06-17 19:21:44 Re: LGPL