From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>, "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 14:38:34 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE6C76CE@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > It wouldn't just be "default to connect to", it would also be
> > "location for tools to store cluster-wide information". Which makes
> > pg_system a slightly more reasonable name in that context, but i
> > certainly have no problem with "default" as a name.
>
> Well, where a tool chooses to install stuff is the business
> of that tool; there isn't any particular reason to think that
> default would suddenly become a preferred choice, I think.
One of the two main reasons to do this was to have a place for tools to
store persistant data in a standard way. At least it was in Daves mail
;-) Actually, two out of three points were data storage.
It is, as you say, up to the tool where to put it. But we should provide
a standard place for tools to do it, to make it easier for both tool
makers and end users.
> I dislike the name pg_system because it implies that that DB
> is somehow special from the point of view of the system ...
> which is exactly what it would *not* be.
That I can certainly agree with.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2005-06-17 15:32:47 | Re: Utility database (Was: RE: Autovacuum in the backend) |
Previous Message | Rod Taylor | 2005-06-17 14:35:48 | Re: Autovacuum in the backend |