Re: Fix a possible typo in rewriteheap.c code comments - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Fix a possible typo in rewriteheap.c code comments
Date
Msg-id CAA4eK1K1368s-ynP9x=qdFuzeZ00imar979aAV9bEbgrOaWCAA@mail.gmail.com
Whole thread Raw
In response to Fix a possible typo in rewriteheap.c code comments  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: Fix a possible typo in rewriteheap.c code comments
List pgsql-hackers
On Mon, Jan 10, 2022 at 9:42 AM Bharath Rupireddy
<bharath.rupireddyforpostgres@gmail.com> wrote:
>
> Hi,
>
> It looks like there's a typo, attaching a tiny patch to fix it.
>
>   *
>   * When doing logical decoding - which relies on using cmin/cmax of catalog
>   * tuples, via xl_heap_new_cid records - heap rewrites have to log enough
> - * information to allow the decoding backend to updates its internal mapping
> + * information to allow the decoding backend to update its internal mapping
>

LGTM.

-- 
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: Multiple Query IDs for a rewritten parse tree
Next
From: Jaime Casanova
Date:
Subject: Re: Is it correct to update db state in control file as "shutting down" during end-of-recovery checkpoint?