Re: Tablespace

From: Decibel! <decibel(at)decibel(dot)org>
To: RPK <rpk(dot)general(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Tablespace
Date: 2007-08-07 22:41:24
Message-ID: 20070807224124.GW25704@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Aug 05, 2007 at 04:03:10AM -0700, RPK wrote:
>
> When PGSQL is installed, it creates two default tablespaces, postgres and

There is no postgres tablespace, only a database. The other default
tablespace is pg_global.

> pg_default. When a user creates a new database he is opted to select a
> tablespace from the above two. Do I need to create a different tablespace
> before creating a database in order to prevent playing with these default

No, it's perfectly fine to store stuff in pg_default. It's what probably
99% of installs do.

> tablespaces? While backing up the database, with a new tablespace, is new
> tablespace also backed up and automatically created when the backup is
> restored on another machine?

Tablespaces are "global" or cluster-wide objects. As such, pg_dump will
not do anything with them. You'd need to use pg_dumpall.

There's a whole different set of concerns with tablespaces and PITR.

Unless you have a real need for tablespaces, just stick with the
defaults.
--
Decibel!, aka Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Decibel! 2007-08-07 22:46:09 Re: array_to_set functions
Previous Message Owen Hartnett 2007-08-07 22:22:36 Re: Take your postgresSql on the road, and live to tell of it.