Re: How to _really_use a non-default tablespace

From: "Andras Simon" <szajmi(at)gmail(dot)com>
To: "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Andras Simon" <szajmi(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: How to _really_use a non-default tablespace
Date: 2006-10-17 15:54:42
Message-ID: 9008cd5d0610170854w282e1870t1d589fbd0f8d4a60@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/17/06, Martijn van Oosterhout <kleptog(at)svana(dot)org> wrote:
> On Tue, Oct 17, 2006 at 04:56:09PM +0200, Andras Simon wrote:
> > As a more drastic example: I created a DB on a tablespace TS, and
> > copied a 25 MB file into one of its tables. I ended up having 60
> > MB of extra data in $PGDATA/pg_xlog that doesn't go away even
> > after dropping the database.
>
> The xlog is not split by database, all databases share the same xlog.

OK, I see. The question then is how far does it grow. If its size is
comparable to that of the actual data, then having separate
tablespaces is not as useful as it first seemed to me. But I might be
missing something.

And there's still the question of indices...

Thanks,

Andras

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-10-17 15:58:31 Re: How to _really_use a non-default tablespace
Previous Message Madison Kelly 2006-10-17 15:41:44 Re: A query planner that learns