pgsql: Renumber confusing value for GUC_UNIT_BYTE - Mailing list pgsql-committers

From Peter Eisentraut
Subject pgsql: Renumber confusing value for GUC_UNIT_BYTE
Date
Msg-id E1oVr5S-001pXf-Jc@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Renumber confusing value for GUC_UNIT_BYTE

It had a power-of-two value, which looks right, and causes the other
values which aren't powers-of-two to look wrong.  But this is tested
for equality and not a bitwise test.

See also:
6e7baa322773ff8c79d4d8883c99fdeff5bfa679
https://www.postgresql.org/message-id/CAOG9ApEu8bXVwBxkOO9J7ZpM76TASK_vFMEEiCEjwhMmSLiaqQ%40mail.gmail.com

Author: Justin Pryzby <pryzby@telsasoft.com>
Discussion: https://www.postgresql.org/message-id/flat/20220720145220.GJ12702@telsasoft.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/3fe76ab9722c2891855dd2b34261f7c23a2e5b2b

Modified Files
--------------
src/include/utils/guc.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)


pgsql-committers by date:

Previous
From: David Rowley
Date:
Subject: pgsql: Make more effort to put a sentinel at the end of allocated memor
Next
From: Justin Pryzby
Date:
Subject: Re: [PATCH] Renumber confusing value for GUC_UNIT_BYTE