If you are using Linux and you want to do things these ways, you can take
advantage loopback files systems. You can carve up a large disk this way and
control the space requirements per client.
Quoting Jeff Davis [EMAIL PROTECTED]:
I must not have been clear. In postgres you can limit people
You might be interested to see a previous thread started by me on that
very subject:
http://archives.postgresql.org/pgsql-general/2004-04/msg00365.php
I got one reply that was very informative by William White:
http://archives.postgresql.org/pgsql-general/2004-04/msg00366.php
The other reply
I'd just like to add that having all the users in one database has
another minor disadvantage:
If you want to make use of PITR for your clients, and client A shares a
postgres instance with client B, and client A asks to be time warped,
then you have to time warp both, since both are in the same
Not sure what overhead - but Oracle has this ;) Infact Oracle by
default puts each user in their own schema, and each user can be
assigned a default tablespace as a property of the user. With the
advent of Tablespace in pg 8.0, is it possible to set a user's default
tablespace?
Alex Turner
Alex Turner [EMAIL PROTECTED] writes:
... With the
advent of Tablespace in pg 8.0, is it possible to set a user's default
tablespace?
ALTER USER user1 SET default_tablespace = foo;
regards, tom lane
---(end of
I must not have been clear. In postgres you can limit people to a
tablespace (in 8.0 of course). You do this by giving them a database
with a default tablespace, and only give them permission on that default
tablespace. That works fine.
The problem is, there is no limit to the size of a
On Wed, 2005-01-05 at 21:34, Jeff Davis wrote:
Benefits of multiple instances:
(1) Let's say you're using the one-instance method and one of your web
users is a less-than-talented developer, and makes an infinite loop that
fills the database with garbage. Not only will that hurt performance,
That's an interesting idea. First, you can't (as far as I know) do it
with just schemas to seperate the users. There is no default tablespace
for an object created inside a given schema.
However, there is a default tablespace for a given database. You can (as
superuser) create a tablespace and
In a typical setup, you might do:
Edit pg_hba.conf to allow connections to the database sameuser which
is a special word meaning that the user can only connect to a database
of the same name.
Then, for each webhosting account you make (let's say the user is named
foo with password bar), execute
Jeff Davis wrote:
However, for truly good seperation, I recommend that you run a seperate
instance of postgresql (with a seperate $PGDATA directory) for each
user, and run it under the UID of that user. It requires a little more
disk space per account, but in a dollar amount it's virtually zero
On Jan 5, 2005, at 9:49 AM, Alan Garrison wrote:
Out of curiosity, what kind of performance hit (whether CPU, memory,
disk activity) is incurred with having a lot of postmasters running in
this kind of a setup versus one postmaster with lots of databases? We
typically run one postmaster for a
Benefits of multiple instances:
(1) Let's say you're using the one-instance method and one of your web
users is a less-than-talented developer, and makes an infinite loop that
fills the database with garbage. Not only will that hurt performance,
but if it fills the disk than no other users can
On Wed, 2005-01-05 at 13:52 -0500, Jeff wrote:
[snip]
You'd have to have separate shared buffers for each which would eat
away from the filesystem cache. Not to mention overhead of having
many more PG's running (in terms of just processes htat need to be
managed and memory used by each).
how about to have only one DB with multiple DB shcemas and assign a
DB user per schema?
Will this solution use the multiple CPUs ? - I think it should
this is my 2cents.
--- Jeff Davis [EMAIL PROTECTED] wrote:
Benefits of multiple instances:
(1) Let's say you're using the one-instance
On Wed, 2005-01-05 at 12:34 -0800, Jeff Davis wrote:
Benefits of multiple instances:
(1) Let's say you're using the one-instance method and one of your web
users is a less-than-talented developer, and makes an infinite loop that
fills the database with garbage. Not only will that hurt
hello,
we have some webhosting servers and we can start postgresql support...
I need to create for one webhosting account one postgresql account,
which will have access only to databases created byh this postgresql
account.
I know, that it is no problem in mysql...
thanx, miso
16 matches
Mail list logo
