Re: Disk I/O Question

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: teeeebro <terryb(at)esi(dot)net>
Cc: "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Disk I/O Question
Date: 2015-11-10 15:28:10
Message-ID: CAFj8pRDxSRGmdzUvdNLMQBAVHsEZ+RvGuqik4vvbeC12Ky8O1A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2015-11-10 15:34 GMT+01:00 teeeebro <terryb(at)esi(dot)net>:

> Hello - I am new to this forum and know nothing about PostgreSQL. I have
> managed Microsoft SQL for 15 years (I know ....)
>
> We have a third party application that uses PostgreSQL for the database
> engine. Performance writing to our Dell Compellent SAN is lacking.
>
> What I've read about PostgreSQL is that it's a single-thread disk I/O
> system
> where only one read/write operation executes at a time.
>

it is 100% isn't true - any client can read data, writer/wal-writer,
autovacum can write

Regards

Pavel

>
> Can you tell me if this is correct?
>
> Thanks!!
> Terry
>
>
>
> --
> View this message in context:
> http://postgresql.nabble.com/Disk-I-O-Question-tp5873364.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bradley, Christie D 2015-11-10 15:30:02 Re: Debugger locks up
Previous Message Bradley, Christie D 2015-11-10 15:24:24 Debugger locks up