| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Subject: | Re: Improve WALRead() to suck data directly from WAL buffers when possible |
| Date: | 2024-01-20 01:47:57 |
| Message-ID: | 60727ac9d5da9330bb4bea0c691fec2ce37296ca.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2024-01-10 at 19:59 +0530, Bharath Rupireddy wrote:
> I've addressed the above review comments and attached v19 patch-set.
Regarding:
- if (!WALRead(state, cur_page, targetPagePtr, XLOG_BLCKSZ, tli,
- &errinfo))
+ if (!WALRead(state, cur_page, targetPagePtr, count, tli,
&errinfo))
I'd like to understand the reason it was using XLOG_BLCKSZ before. Was
it a performance optimization? Or was it to zero the remainder of the
caller's buffer (readBuf)? Or something else?
If it was to zero the remainder of the caller's buffer, then we should
explicitly make that the caller's responsibility.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2024-01-20 01:53:36 | Re: Documentation for building with meson |
| Previous Message | Jeff Davis | 2024-01-20 00:13:18 | Re: Change GUC hashtable to use simplehash? |