| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Cc: | "'Adir Shaban *EXTERN*'" <adirshaban1995(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Database fixed size |
| Date: | 2016-09-28 12:31:22 |
| Message-ID: | 14230.1475065882@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> writes:
> Adir Shaban wrote:
>> Is there anyway to limit a database size?
>> For example, I need to create a database for user X and I don't want it to use more than 5 GB.
> You can create a tablespace on a device with limited size.
> Then you can create the database on that tablespace.
Note the reference to tablespace. It's unwise to just put the whole
cluster on a tiny device (or equivalently, attempt to solve this with
OS-level disk quotas applied to the whole installation). The reason is
that PG gets very unhappy if it runs out of WAL space. Hitting a limit
on table size per se behaves a bit more sanely, though even there you
can get into trouble --- for instance, in some situations VACUUM will
try to allocate additional disk space, making recovery harder.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Sofen | 2016-09-28 12:34:10 | Re: how to monitor the progress of really large bulk operations? |
| Previous Message | Alexander Farber | 2016-09-28 12:18:05 | Re: isnull() function in pgAdmin3 |