Skip site navigation (1) Skip section navigation (2)

Re: Physical Database Configuration

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Guy Rouillier <guyr(at)masergy(dot)com>
Cc: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Physical Database Configuration
Date: 2004-03-26 18:36:05
Message-ID: Pine.LNX.4.33.0403261135210.7399-100000@css120.ihs.com (view raw or flat)
Thread:
Lists: pgsql-general
On Fri, 26 Mar 2004, Guy Rouillier wrote:

> (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.

Not really, but there's more than one way to skin a cat.

What you can do is create a table for each month, then create a view on 
top of those tables.


In response to

pgsql-general by date

Next:From: Stephan SzaboDate: 2004-03-26 19:04:26
Subject: Re: simple join query runs very slowly
Previous:From: Bruce MomjianDate: 2004-03-26 18:24:33
Subject: Re: 7.4.2 on Solaris 9 - Error

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group