Re: WAL usage calculation patch
| От | Amit Kapila |
|---|---|
| Тема | Re: WAL usage calculation patch |
| Дата | |
| Msg-id | CAA4eK1LjkwGOegWMfs3tggD3-BXLzyZXFz7qBZaf_yLBPjZdHQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: WAL usage calculation patch (Dilip Kumar <dilipbalaut@gmail.com>) |
| Ответы |
Re: WAL usage calculation patch
|
| Список | pgsql-hackers |
On Fri, Apr 3, 2020 at 8:55 AM Dilip Kumar <dilipbalaut@gmail.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
В списке pgsql-hackers по дате отправления: