Re: any impact to DML sql statements when checkpoint starting

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "James Pang (chaolpan)" <chaolpan(at)cisco(dot)com>
Cc: "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: any impact to DML sql statements when checkpoint starting
Date: 2022-02-04 00:35:19
Message-ID: CAKFQuwbiYtEaiv-Q-Zj_h+g0jp0s6SfB15_EdXG=bZ_VuuDb+A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Thu, Feb 3, 2022 at 5:29 PM James Pang (chaolpan) <chaolpan(at)cisco(dot)com>
wrote:

> Any impact to DML(insert,update,delete,commit) when checkpoint starting
> , not sure any lock waiting ?
>
>
>
Checkpoints consume disk I/O. If the pages your DML are touching are not
already in shared memory, getting them there also consumes I/O. The WAL
writing consumes I/O.
I would expect some possible (but I'd think minor) contention if
the changes are touching the same buffer pages that are being flushed to
disk. But pages are fairly small individually.

David J.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message James Pang (chaolpan) 2022-02-04 00:45:44 RE: any impact to DML sql statements when checkpoint starting
Previous Message James Pang (chaolpan) 2022-02-04 00:28:43 any impact to DML sql statements when checkpoint starting