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 CAA4eK1LLx7k70+R+KBZDgSNAJ7EH0cXYk8X97KT0rSicOYti0g@mail.gmail.com
Whole thread Raw
In response to Re: Fix a possible typo in rewriteheap.c code comments  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Mon, Jan 10, 2022 at 10:22 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> 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.
>

Pushed.

-- 
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Improve error handling of HMAC computations and SCRAM
Next
From: Masahiko Sawada
Date:
Subject: Re: Skipping logical replication transactions on subscriber side