| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: wait events for disk I/O |
| Date: | 2017-03-07 15:46:23 |
| Message-ID: | CA+Tgmoax0RWf_fSOxOmbL01eH0Rp7i0sXjtCNDr0hu-_QvAOEw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 6, 2017 at 9:09 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> Sure, if you think both Writes and Reads at OS level can have some
> chance of blocking in obscure cases, then we should add a wait event
> for them.
I think writes have a chance of blocking in cases even in cases that
are not very obscure at all.
>> I think somebody should try a pgbench run with this patch applied,
>> using a scale factor greater than shared_buffers, and generate a wait
>> event profile, just to see if these are showing up and how often.
>
> Yeah, that makes sense to me and we should try for both read-write and
> read-only tests.
wfm.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-03-07 15:49:34 | Re: WIP: Faster Expression Processing v4 |
| Previous Message | Fujii Masao | 2017-03-07 15:45:44 | ALTER PUBLICATION and segmentation fault |