From: | "Campano, Troy" <Troy(dot)Campano(at)LibertyMutual(dot)com> |
---|---|
To: | "Richard Huxton" <dev(at)archonet(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | "Postgres general mailing list" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Database Size Limiting |
Date: | 2004-05-27 19:57:32 |
Message-ID: | 82C3FD729CFA504CA44E7D32BDED411F0A2EF0F4@lm-exmsg-07.lm.lmig.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Is it possible to have a database spread across two data files?
So if it fills up filesystem1 then we could add a second filesystem and
allow it to grow onto this second filesystem?
Thanks!
-----Original Message-----
From: Richard Huxton [mailto:dev(at)archonet(dot)com]
Sent: Thursday, May 27, 2004 3:23 PM
To: Joshua D. Drake
Cc: Campano, Troy; Postgres general mailing list
Subject: Re: [GENERAL] Database Size Limiting
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 | Phil Berman | 2004-05-27 20:10:41 | Postgres on Solaris 10 |
Previous Message | Mark Harrison | 2004-05-27 19:41:03 | HOWTO: Integrating Posgresql queries into an event loop |