From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Better I/O throughput? (was Re: create tablespace - cannot run inside a transaction block)
Date: Wed, 25 Sep 2019 14:40:35 -0500
Message-ID: <2a5bed6e-9cc2-9832-0588-8b601e00d5e5@gmail.com> (raw)
In-Reply-To: <19fd8930b2fcc8f05737b54c8ec847e486dda687.camel@cybertec.at>
References: <1709062667.8516797.1569423052743.ref@mail.yahoo.com>
<1709062667.8516797.1569423052743@mail.yahoo.com>
<19fd8930b2fcc8f05737b54c8ec847e486dda687.camel@cybertec.at>
On 9/25/19 2:16 PM, Laurenz Albe wrote:
> On Wed, 2019-09-25 at 14:50 +0000, Pepe TD Vo wrote:
>> Normally, in Oracle we need to create database, tablespace then
>> username/schema and tables, objects, etc...
>>
>> is the procedure as same as in Postgres? I see the login and schema
>> are totally different in Postgres.
> 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?
(A long-running synchronous IO request seems it would block everything
behind it, whereas objects in tablespaces on different devices could still
be queried.)
--
Angular momentum makes the world go 'round.
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-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Better I/O throughput? (was Re: create tablespace - cannot run inside a transaction block)
In-Reply-To: <2a5bed6e-9cc2-9832-0588-8b601e00d5e5@gmail.com>
* 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