Re: Make mesage at end-of-recovery less scary.
| От | Ashutosh Sharma |
|---|---|
| Тема | Re: Make mesage at end-of-recovery less scary. |
| Дата | |
| Msg-id | CAE9k0PkCQzKq1nOUb_Wd2VjtapUYV80sx8DbPGn8ULBebpKgyQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Make mesage at end-of-recovery less scary. (Kyotaro Horiguchi <horikyota.ntt@gmail.com>) |
| Ответы |
Re: Make mesage at end-of-recovery less scary.
|
| Список | pgsql-hackers |
On Wed, Mar 2, 2022 at 7:47 AM Kyotaro Horiguchi
<horikyota.ntt@gmail.com> wrote:
>
> At Sat, 19 Feb 2022 09:31:33 +0530, Ashutosh Sharma <ashu.coek88@gmail.com> wrote in
> > The changes looks good. thanks.!
>
> Thanks!
>
> Some recent core change changed WAL insertion speed during the TAP
> test and revealed one forgotton case of EndOfWAL. When a record
> header flows into the next page, XLogReadRecord does separate check
> from ValidXLogRecordHeader by itself.
>
The new changes made in the patch look good. Thanks to the recent
changes to speed WAL insertion that have helped us catch this bug.
One small comment:
record = (XLogRecord *) (state->readBuf + RecPtr % XLOG_BLCKSZ);
- total_len = record->xl_tot_len;
Do you think we need to change the position of the comments written
for above code that says:
/*
* Read the record length.
*
...
...
--
With Regards,
Ashutosh Sharma.
В списке pgsql-hackers по дате отправления: