Re: Utility database (Was: RE: Autovacuum in the backend) - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Utility database (Was: RE: Autovacuum in the backend)
Date
Msg-id 42B28E07.8010508@familyhealth.com.au
Whole thread Raw
In response to Re: Utility database (Was: RE: Autovacuum in the backend)  ("Magnus Hagander" <mha@sollentuna.net>)
Responses Re: Utility database (Was: RE: Autovacuum in the backend)
List 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



pgsql-hackers by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: Utility database (Was: RE: Autovacuum in the backend)
Next
From: Russell Smith
Date:
Subject: Re: Autovacuum in the backend