| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Cc: | Julien Rouhaud <rjuju123(at)gmail(dot)com>, Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Kirill Bychik <kirill(dot)bychik(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | Re: WAL usage calculation patch |
| Date: | 2020-04-03 03:32:41 |
| Message-ID: | CAA4eK1LjkwGOegWMfs3tggD3-BXLzyZXFz7qBZaf_yLBPjZdHQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 3, 2020 at 8:55 AM Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
>
> I think now I got the reason. Basically, both of these records are
> storing the FPW, and FPW size can vary based on the hole size on the
> page. If hold size is smaller the image length will be more, the
> image_len= BLCKSZ-hole_size. So in subsequent records, the image size
> is bigger.
>
This means if we always re-create the database or may be keep
full_page_writes to off, then we should get consistent WAL usage data
for all tests.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-04-03 03:40:51 | Re: [PATCH] Keeps tracking the uniqueness with UniqueKey |
| Previous Message | Fujii Masao | 2020-04-03 03:28:03 | Re: Some problems of recovery conflict wait events |