From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Fernando Schapachnik <fschapachnik(at)vianetworks(dot)com(dot)ar> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Database quota |
Date: | 2002-03-05 23:33:05 |
Message-ID: | 19364.1015371185@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Fernando Schapachnik <fschapachnik(at)vianetworks(dot)com(dot)ar> writes:
> Is there any way to stablish a maximum size for a database? Would
> setting each database directory to user:pgsql, 770 and setting a file
> system quota for user "user" work? I mean, would postmaster handle
> the limit gracefully?
If you can exclude pg_xlog and pg_clog from the quota, I believe that
failure to extend other tables would be reasonably graceful. Failure to
extend the log files will cause a system stop, however. (The good news
is that the sizes of the log file directories are fairly predictable.
Log file segments are recycled when no longer needed, so the total space
used doesn't really grow without bound, at least not in 7.2.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-03-06 00:06:54 | Re: Archiver(custom): could not initialize compression library - (null) |
Previous Message | Art Nicewick | 2002-03-05 23:12:40 | [GENERAL] Tricking postgresql to do a oracle-like stored Procedure |