Re: Better I/O throughput? (was Re: create tablespace - cannot run inside a transaction block)

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Better I/O throughput? (was Re: create tablespace - cannot run inside a transaction block)
Date: 2019-09-26 18:57:17
Message-ID: 471e8349b8b0839a108ae28c00adb7c2de42d657.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wed, 2019-09-25 at 14:40 -0500, Ron wrote:
> > No, normally you don't create tablespaces in PostgreSQL.
> > They are a few use cases for them, but not many.
>
> Do I/O requests in the Linux kernel get "backlogged" when they all
> hit the
> same device? Or would you get better throughput (or less latency)
> by
> spreading the load across multiple devices?

Sure, spreading I/O across multiple devices is one use case for
tablespaces. But usually this is easier to do by striping a
logical volume across several physical volumes at a lower level.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Ekaterina Amez 2019-09-27 14:23:39 Files overwritten when installing v9.6 in machine with v8.4 previously running
Previous Message Bashir Jahed 2019-09-26 07:39:00 AWS IAM Role Authentication Integration