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-11 05:26:19
Message-ID: CAA4eK1LLx7k70+R+KBZDgSNAJ7EH0cXYk8X97KT0rSicOYti0g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 10, 2022 at 10:22 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> 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.
>

Pushed.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-01-11 05:42:52 Re: Use -fvisibility=hidden for shared libraries
Previous Message Michael Paquier 2022-01-11 04:56:22 Improve error handling of HMAC computations and SCRAM