![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello all, I have accidently :-) found 'initlocation' and now I like to know, how many secondary database i can create. I like to do that, because I have a Virtual Webserver and for each VirtualHost I have a local $USER. Now I like to create seperatly secondary databases for each $USER/VHost. Thanks Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/88452356 67100 Strasbourg/France IRC #Debian (irc.icq.com) |
|
Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a tool for doing 5% of the work and then sitting around waiting for someone else to do the other 95% so you can sue them. |
#3
| |||
| |||
|
|
As many as you have disk space for I guess. You might need one postmaster per location but I'm not sure about that, check the docs... |
#4
| |||
| |||
|
|
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. |

Each user
#5
| |||
| |||
|
|
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, |
#6
| |||||
| |||||
|
|
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. |
2) one pgsql database per user. Probably most common. Each userhas full pgsql database at her disposal. It's a bit hard to manage quotas, dbsize comes in handy but it involeves creating some sort of "quota enforcing" daemon... |
|
3) one pgsql database with one schema per user. Interesting, can very easily create many "databases", does not give full pgsql power, harder to manage quotas than previous model... |
|
Hmm, I wonder what are the feelings of people using such models. I did not use them, so I have no idea. And I wonder how problematic is "quota enforcement" there.... |
|
Regards. Dawid |
#7
| |||
| |||
|
|
Dawid Kuroczko wrote: 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 |
![]() |
| Thread Tools | |
| Display Modes | |
| |