From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Michael Paquier <michael(at)paquier(dot)xyz>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com> |
Subject: | Re: Cleaning up nbtree after logical decoding on standby work |
Date: | 2023-06-08 01:10:00 |
Message-ID: | CAH2-Wzkugd17Hz9SaPjsoCLzgztX8Uy++OM4tv9d3D4jkmEUEw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jun 7, 2023 at 5:12 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> -1. For me separating the P_NEW path makes a lot of sense, but isn't 16
> material. I don't agree that it's a problem to have heaprel as a parameter in
> a bunch of places that don't strictly need it today.
As I've said, this is primarily about keeping all of the branches
consistent. I agree that there is no particular known consequence to
not doing this, and have said as much several times.
> I don't really understand why the patch does s/heaprel/heapRel/.
That has been the style used within nbtree for many years now.
> Most of these
> functions aren't actually using camelcase parameters? This part of the change
> just blows up the size, making it harder to review.
I wonder what made it impossibly hard to review the first time around.
The nbtree aspects of this work were pretty much written on
auto-pilot. I had no intention of making a fuss about it, but then I
never expected this push back.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2023-06-08 01:45:07 | Re: win32ver data in meson-built postgres.exe |
Previous Message | Masahiko Sawada | 2023-06-08 01:01:27 | Re: running logical replication as the subscription owner |