We use Postgres for shared hosting; i.e. what most people use MySQL for.
The biggest headache for us so far has been that we're unable to get
group permissions set up effectively so that different groups of
customers, admins, apaches, etc. can access/modify the data they need,
without manual intervention from someone with root and a relatively deep
knowledge of the permissions system.
I posted about this a while ago, and I promised to step back and come up
with an example of the type of situation I'm talking about. It's not
perfect, but if I don't post it now, it'll never get finished:
https://github.com/mjorlitzky/postgres-groups
This is a "test suite" for the sort of behavior I'd like to achieve.
I've tried to explain what I want in the README, and I've implemented it
in the filesystem with only 4 commands. The closest I was able to come
in Postgres is a mess (see pg-test/02-create-permissions.sh), and
doesn't work when we add a new user in
pg-test/04-add-new-user-and-retest.sh.
First, if I'm just overlooking something, I'd really like to know how I
can make this work in 02-create-permissions.sh! If not, consider this a
feature request that would make Postgres much more popular on shared hosts.
I'll answer any questions on- or off-list; like I said, it ain't
perfect, but it attained a permanent spot somewhere in the middle of my
todo list so I'm posting it as-is.
**THIS WILL ADD SYSTEM USERS AND MESS WITH YOUR LOCAL POSTGRES INSTALL**
It will clean up after itself and should be safe, but please read the
scripts before you run them as root.