| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | "Campano, Troy" <Troy(dot)Campano(at)LibertyMutual(dot)com>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Database Size Limiting |
| Date: | 2004-05-27 19:22:57 |
| Message-ID: | 40B64011.4000209@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Joshua D. Drake wrote:
> Hello,
>
> You could use Filsystem quotas but I strongly suggest against it as it
> will probably bring about database corruption.
Ah - manual reference
http://www.postgresql.org/docs/current/static/disk-full.html
"24.2. Disk Full Failure
The most important disk monitoring task of a database administrator is
to make sure the disk doesn't grow full. A filled data disk may result
in subsequent corruption of database indexes, but not of the tables
themselves. If the WAL files are on the same disk (as is the case for a
default configuration) then a filled disk during database initialization
may result in corrupted or incomplete WAL files. This failure condition
is detected and the database server will refuse to start up. "
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matt Van Mater | 2004-05-27 19:30:40 | Re: Connection log entries - random port number recorded |
| Previous Message | Greg Spiegelberg | 2004-05-27 19:17:55 | Re: Clustering Postgres |