Re: Fix comments in gistxlogDelete, xl_heap_freeze_page and xl_btree_delete

From: "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fix comments in gistxlogDelete, xl_heap_freeze_page and xl_btree_delete
Date: 2023-03-04 08:33:45
Message-ID: 15ea46fc-bbf2-cadc-df1d-dd4a418d52b2@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 3/3/23 6:53 PM, Robert Haas wrote:
> On Fri, Mar 3, 2023 at 11:28 AM Drouvot, Bertrand
> <bertranddrouvot(dot)pg(at)gmail(dot)com> wrote:
>> Thanks for having looked at it!
>
> +1. Committed.
>

Thanks!

Not a big deal, but the commit message that has been used is not 100% accurate.

Indeed, for gistxlogDelete, that's the other way around (as
compare to what the commit message says).

Regards,

--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2023-03-04 10:33:53 Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher
Previous Message Amit Kapila 2023-03-04 06:13:39 Re: pg_upgrade and logical replication