Dawid Kuroczko wrote:
On Fri, 12 Nov 2004 17:20:59 +0100, Michelle Konzack
<linux4michelle@freenet.de> wrote:
Please note, that I do not run seperatly databases.
I like only to split it per $USER physicaly from the main database.
I like to have this setup for my new Virtual-Webserver where I have
for each VHost a local $USER.
Some time ago I talked with a friend working at some ISP, and we were
talking about PostgreSQL's superiority to hmm, other RDBMSs... ;)
Blah, blah, blah. The question is - how to give many many users
access to PostgreSQL... I see three approaches, and all of these
have pros and cons.
1) One pgsql per user -- in other words each user runs its own copy of
pgsql -- waste of memory (each user having its own shared mem, etc),
but can enforce quota limits, etc. Hard to keep all those copies of
pgsql running.
Hello,
We use this version as it allows us to provide the best security
and flexibility to the customer
Sincerely,
Joshua D. Drake
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
begin:vcard
fn:Joshua Drake
n:Drake;Joshua
org:Command Prompt, Inc.
adr:;;PO Box 215 ;Cascade Locks;OR;97014;US
email;internet:jd@commandprompt.com
title:Consultant
tel;work:503-667-4564
tel;fax:503-210-0334
x-mozilla-html:FALSE
url:http://www.commandprompt.com
version:2.1
end:vcard
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
