Re: temp tablespaces and SSDs, etc..

Lists: pgsql-performance
From: Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>
To: pgsql-performance(at)postgresql(dot)org
Subject: temp tablespaces and SSDs, etc..
Date: 2013-02-08 20:52:37
Message-ID: CAKuK5J3uYTFaWk4ep2XNZHyVm7t4hLPoJWZ_GZi+j92jg=e6pg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-performance

I was wondering if somebody could clear up how tablespaces are used.
Let's say I have three classes of storage:
- ramdisk (tmpfs)
- SSD
- spinning rust

Furthermore, let's say I'd like to be able to tell postgresql to
prefer them - in that order - until they each get full. IE, use tmpfs
until it reports ENOSPC and then fall back to SSD, finally falling
back to spinning rust. Is there a way to do this?

--
Jon


From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: temp tablespaces and SSDs, etc..
Date: 2013-02-16 00:32:38
Message-ID: 20130216003238.GB12029@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-performance

On Fri, Feb 8, 2013 at 02:52:37PM -0600, Jon Nelson wrote:
> I was wondering if somebody could clear up how tablespaces are used.
> Let's say I have three classes of storage:
> - ramdisk (tmpfs)
> - SSD
> - spinning rust
>
> Furthermore, let's say I'd like to be able to tell postgresql to
> prefer them - in that order - until they each get full. IE, use tmpfs
> until it reports ENOSPC and then fall back to SSD, finally falling
> back to spinning rust. Is there a way to do this?

Nope.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +