From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Nicolas PARIS <nicolas(dot)paris(at)riseup(dot)net> |
Cc: | Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
Subject: | Re: tablespace to benefit from ssd ? |
Date: | 2020-02-20 17:30:43 |
Message-ID: | CAMkU=1y6y25GLgcL+2DZt4J8+x=9tZy5kXA2sz5Uy5u-G5vRgA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, Feb 18, 2020, 11:42 PM Nicolas PARIS <nicolas(dot)paris(at)riseup(dot)net>
wrote:
> However the server has a large amount of ram
> memory and I suspect all of those indexes are already cached in ram.
>
Then there may be no benefit to be had.
>
> I have read that tablespaces introduce overhead of maintenance and
> introduce complication for replication.
Yes, they are a nuisance for the humans who need to document, maintain,
configure, etc. And they can induce administrators into making mistakes
which can prolong outages or cause data loss.
But on the other hand I have
> this ssd disk ready for something.
>
That isn't a good reason. Unless your users are complaining, or you think
they will be soon as things scale up, or you think they would be
complaining of they weren't too apathetic to, then I would make no change
that adds complexity just because the hardware exists.
But I would turn on track_io_timing, and load pg_stat_statements, and
probably set up auto_explain. That way when problems do arrive, you will
be prepared to tackle them with empirical data.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Daulat Ram | 2020-02-21 05:34:21 | Can we have multiple tablespaces with in a database. |
Previous Message | Lars Aksel Opsahl | 2020-02-20 09:20:50 | Re: SubtransControlLock and performance problems |