From: Tom Lane <tgl@sss.pgh.pa.us>
To: dave.bath@unix.net
Cc: pgsql-admin@postgresql.org
Subject: Re: Pre-allocation of space: a business rationale
Date: Wed, 02 Nov 2005 22:48:00 -0500
Message-ID: <17603.1130989680@sss.pgh.pa.us> (raw)
In-Reply-To: <200511031427.10391.dave.bath@unix.net>
References: <C45835824D00A844BBD0F032D5CDED9202D55552@pisgana01sxch01.ana.firstamdata.com>
<21438.1130817553@sss.pgh.pa.us>
<200511021400.05346.xzilla@users.sourceforge.net>
<200511031427.10391.dave.bath@unix.net>
"Bath, David" <dave.bath@unix.net> writes:
> C) I want to avoid the possibility of uncontrolled growth of luser data
> blowing disk leading to stoppage of 24x7 data.
You put the luser data and the critical data into separate tablespaces
that are in separate partitions (filesystems). End of problem ...
(And no, I don't believe in having Postgres reinvent filesystem-level
functionality. If you didn't set up appropriate hard partitions,
consider a loopback filesystem for your tablespace.)
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, dave.bath@unix.net
Subject: Re: Pre-allocation of space: a business rationale
In-Reply-To: <17603.1130989680@sss.pgh.pa.us>
References: <C45835824D00A844BBD0F032D5CDED9202D55552@pisgana01sxch01.ana.firstamdata.com> <21438.1130817553@sss.pgh.pa.us> <200511021400.05346.xzilla@users.sourceforge.net> <200511031427.10391.dave.bath@unix.net> <17603.1130989680@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox