From: | Jeff <threshar(at)torgo(dot)978(dot)org> |
---|---|
To: | Alan Garrison <alang(at)cronosys(dot)com> |
Cc: | PgSQL General List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL users on webhosting |
Date: | 2005-01-05 18:52:59 |
Message-ID: | 052AD5CC-5F4B-11D9-9B47-000D9366F0C4@torgo.978.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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 lot of
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). You'd also have to have the users
connect to PG on an alternate port and that may irritate some.
In a web hosting (multi-user) environment it may make more sense. but
you could also just give each user his own db and only allow sameuser
access to each db via pg_hba.conf.
--
Jeff Trout <jeff(at)jefftrout(dot)com>
http://www.jefftrout.com/
http://www.stuarthamm.net/
From | Date | Subject | |
---|---|---|---|
Next Message | Joost Kraaijeveld | 2005-01-05 19:15:28 | Index on a view?? |
Previous Message | Bruno Wolff III | 2005-01-05 18:52:50 | Re: warning: pg_query(): Query failed |