Re: Table spaces again [was Re: Threaded Sorting] - Mailing list pgsql-hackers

From Michael Paesold
Subject Re: Table spaces again [was Re: Threaded Sorting]
Date
Msg-id 002d01c26e24$af3cca70$4201a8c0@beeblebrox
Whole thread Raw
In response to Re: Table spaces again [was Re: Threaded Sorting]  ("Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>)
List pgsql-hackers
Shridhar Daithankar <shridhar_daithankar@persistent.co.in> wrote:
[snip]
> On 7 Oct 2002 at 15:52, Hans-Jürgen Schönig wrote:
[snip]
> > With tablespaces you can assign 30mb to use a, 120mb to user b etc. ...
> > Table spaces are a nice abstraction layer to the file system.
>
> Hmm.. And how does that fit in database metaphor? What practical use is
that? I
> can't imagine as I am a developer and not a DBA.

Virtual hosting at ISP's for example.

> I believe giving each database it's own transaction log would be a great
> advantage of this scheme.

Well, if you think of Tom's recent patch (ganged WAL writes), from a
performance point of view, this would only be good if each transaction
log had it's own disk. Otherwise a single transaction log is still better.

I think tablespaces is a good idea. I also prefer associating tablespaces
with directory structures better over the oracle style.

Regards,
Michael Paesold



pgsql-hackers by date:

Previous
From: Neil Conway
Date:
Subject: Re: Proposed LogWriter Scheme, WAS: Potential Large
Next
From: Alvaro Herrera
Date:
Subject: BTree metapage lock and freelist structure