From: Peter Geoghegan <pg@bowt.ie>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Use nbtdesc "level" field name consistently.
Date: Wed, 19 Apr 2023 19:15:32 +0000
Message-ID: <E1ppDH9-003sZy-Jy@gemulon.postgresql.org> (raw)
Use nbtdesc "level" field name consistently.
The "lev" name that appeared in NEWROOT nbtree record desc output was
inconsistent with the symbol name from the underlying C struct. It was
also inconsistent with nbtdesc output for other nearby record types with
similar level fields.
Standardize on "level" to make everything consistent.
Follow-up to commit 1c453cfd.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/2584639653eec13726a25d6ea8a4b42153185723
Modified Files
--------------
src/backend/access/rmgrdesc/nbtdesc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: pg@bowt.ie, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Use nbtdesc "level" field name consistently.
In-Reply-To: <E1ppDH9-003sZy-Jy@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox