| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | John Browne <jkbrowne(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postgres, tablespaces, and quotas |
| Date: | 2005-05-05 15:10:06 |
| Message-ID: | 23638.1115305806@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
John Browne <jkbrowne(at)gmail(dot)com> writes:
> I was just curious about what would happen given the following scenario:
> - Unix user has their own tablespace (and corresponding database)
> stored in /home/someuser/mydata
> - Quotas are enabled on /home
> - User reaches their quota, effectively causing only this tablespace
> to run out of disk space.
> How would postgres handle this scenario?
It's not tested very often but I think it should work all right ---
insertions and updates into that tablespace might fail but otherwise
no problem.
What you want to watch out for is running out of space for pg_xlog
or pg_clog. Either one will cause a database panic shutdown. No
data loss, but no service either till you free up some space :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rich Shepard | 2005-05-05 15:27:50 | Re: Inserting a record into another table ... inside a |
| Previous Message | Scott Marlowe | 2005-05-05 14:52:31 | Re: postgresql replication |