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

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Magnus Hagander <mha(at)sollentuna(dot)net>
Cc: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, 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 08:47:03
Message-ID: 42B28E07.8010508@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I think this is a very good idea. I've come up against this need once or
> twice before.. And the fact that stuff in template1 gets propagated out
> to all newly created databases can be a major pain when this happens.
>
> A shared database for this stuff would be great - then each tool could
> just create a schema for it's own stuff.
>
> How does pgAdmin deal with this today?

In phpPgAdmin the default db to connect to can be specified per-server
in the config file. It defaults to template1. It actually is not
relevant at all which db it is, so long as they can connect to it.

Chris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Russell Smith 2005-06-17 08:56:17 Re: Autovacuum in the backend
Previous Message Andreas Pflug 2005-06-17 08:43:52 Re: Utility database (Was: RE: Autovacuum in the backend)