Physical Database Configuration

From: "Guy Rouillier" <guyr(at)masergy(dot)com>
To: "PostgreSQL General" <pgsql-general(at)postgresql(dot)org>
Subject: Physical Database Configuration
Date: 2004-03-26 17:53:47
Message-ID: 9593420C5541924EA4C94E5FC164F88803E42B@m-tx-exch01.add0.masergy.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

(Resurrecting a subject I found searching the archives...)

Newbie. We're investigating replacing our Oracle databases with
PostgreSQL. Our largest database is currently 25 GB and growing. It
contains time sequenced data. Under Oracle, we use a partitioned
tablespace for the busiest table, so that we can remove old partitions
after an aging period. This one table is the majority of that 25 GB.

I saw in the referenced sequence of posts that PostgreSQL will close a
file for a table once it reaches 1 GB, and start a new file. So I'm
concluding PostgreSQL has the ability to span multiple files for a
single table. Is there any way for me to control that, so I can get
PostgreSQL to start a new file on the 1st of each month? Or is this
planned for tablespaces, which I also saw discussed.

Thanks.

--
Guy Rouillier

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2004-03-26 18:23:45 Re: Physical Database Configuration
Previous Message Andrew Sullivan 2004-03-26 17:49:36 Re: Questions on production rollout