From: Nicolas PARIS <nicolas.paris@riseup.net>
To: pgsql-performance\@lists.postgresql.org <pgsql-performance@lists.postgresql.org>
Subject: tablespace to benefit from ssd ?
Date: Wed, 19 Feb 2020 05:42:41 +0100
Message-ID: <87ftf7fari.fsf@riseup.net> (raw)
Hi
I have both hdd and ssd disk on the postgres server. The cluster is
right now created on the hdd only. I am considering using a tablespace
to put some highly used postgres object on the ssd disk. Of course the
ssd is small compared to the hdd, and I need to choose carefully what
objects are stored on that side.
I am wondering what kind of object (indexes, data) would benefit from
ssd. The database primary/foreign keys are highly used and there is
almost no sequencial scan. However the server has a large amount of ram
memory and I suspect all of those indexes are already cached in ram.
I have read that tablespaces introduce overhead of maintenance and
introduce complication for replication. But on the other hand I have
this ssd disk ready for something.
Any recommandation ?
--
nicolas paris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: nicolas.paris@riseup.net, pgsql-performance@lists.postgresql.org
Subject: Re: tablespace to benefit from ssd ?
In-Reply-To: <87ftf7fari.fsf@riseup.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox