From: | Dev <dev_hyd2001(at)yahoo(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Best way to limit database sizes |
Date: | 2008-07-03 16:07:23 |
Message-ID: | 619537.42270.qm@web53708.mail.re2.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
I have a single Postgres server which will be hosting multiple databases belonging to different users. What would be the recommendation to limit the size of each of the databases?
I've considered creating a tablespace in a directory owned by the user , so I can use Linux quotas to prevent higher disk usage , but this turned out be a bad thought, as all the files are anyway owned by the postgres user and so disk quotas won't have any effect.
Now I'm contemplating having a cron job which checks the size of each tablespace belonging to a user and somehow informing the admin about db's getting over the threshold size.
Is there anyone who has tried a better way to limit the db sizes ?
cheers
/Dev
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2008-07-03 16:28:17 | Re: Best way to limit database sizes |
Previous Message | Achilleas Mantzios | 2008-07-03 15:08:47 | Re: changing sequence in serial field |