Better I/O throughput? (was Re: create tablespace - cannot run insidea transaction block)
От | Ron |
---|---|
Тема | Better I/O throughput? (was Re: create tablespace - cannot run insidea transaction block) |
Дата | |
Msg-id | 2a5bed6e-9cc2-9832-0588-8b601e00d5e5@gmail.com обсуждение исходный текст |
Ответ на | Re: create tablespace - cannot run inside a transaction block (Laurenz Albe <laurenz.albe@cybertec.at>) |
Ответы |
Re: Better I/O throughput? (was Re: create tablespace - cannot runinside a transaction block)
Re: Better I/O throughput? (was Re: create tablespace - cannot runinside a transaction block) |
Список | pgsql-admin |
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.
В списке pgsql-admin по дате отправления: