From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Dawid Kuroczko <qnex42(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: How many secondary databases can I create? |
Date: | 2004-11-14 05:40:10 |
Message-ID: | 4196EFBA.5040105@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dawid Kuroczko wrote:
>On Fri, 12 Nov 2004 17:20:59 +0100, Michelle Konzack
><linux4michelle(at)freenet(dot)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(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
Attachment | Content-Type | Size |
---|---|---|
jd.vcf | text/x-vcard | 285 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Bopolissimus Platypus Jr | 2004-11-14 05:50:10 | shrinking physical space used |
Previous Message | Michael Fuhr | 2004-11-14 05:29:27 | Re: Value of serial data type after insert. |