Re: Fix a possible typo in rewriteheap.c code comments

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fix a possible typo in rewriteheap.c code comments
Date: 2022-01-10 04:52:30
Message-ID: CAA4eK1K1368s-ynP9x=qdFuzeZ00imar979aAV9bEbgrOaWCAA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 10, 2022 at 9:42 AM Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)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.

In response to

Responses

Browse pgsql-hackers by date

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