From: | <geek+(at)cmu(dot)edu> |
---|---|
To: | Postgres Hackers List <hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Re: CREATE DATABASE |
Date: | 1998-05-18 13:03:43 |
Message-ID: | emacs-smtp-3879-13664-12719-415976@export.andrew.cmu.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Then <lockhart(at)alumni(dot)caltech(dot)edu> spoke up and said:
> That way the Postgres administrator can run initlocation, define an
> environment variable pointing at that alternate location, and then start
> up the backend. Users would have only those previously defined areas to
> work with.
Personally, I don't care *how* alternate locations are
setup/specified, as long as
1) With a single postmaster, I can access databases in all of the
locations.
2) Adding a new location should be reserved to the PostgreSQL
superuser.
3) Adding a new location should *not* require restarting the
postmaster.
Additionally, it would be nice to have syntax available for spreading
a database across multiple locations (a la Ingres).
- --
=====================================================================
| JAVA must have been developed in the wilds of West Virginia. |
| After all, why else would it support only single inheritance?? |
=====================================================================
| Finger geek(at)andrew(dot)cmu(dot)edu for my public key. |
=====================================================================
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQBVAwUBNWAxr4dzVnzma+gdAQEeGQH/c2L/THi6ZpijGz+JyCfnLhgaVnf/CC0Z
w3iX7UEAp1C5Oc/UkmkX3cMZ3cEYkdYAYOBvGtKbhnxO9x90wp5+Mw==
=8QdB
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas G. Lockhart | 1998-05-18 15:20:35 | Re: [HACKERS] Re: [PATCHES] char/varchar locale support |
Previous Message | Hannu Krosing | 1998-05-18 11:48:27 | WWW site kas no mention of interfaces list |