BUG #16403: set_bit function does not have expected effect - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #16403: set_bit function does not have expected effect
Date
Msg-id 16403-c4ad1c176b130a5b@postgresql.org
Whole thread Raw
Responses Re: BUG #16403: set_bit function does not have expected effect
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      16403
Logged by:          Alex Movitz
Email address:      amovitz@bncpu.com
PostgreSQL version: 11.0
Operating system:   Linux
Description:

Input:
SELECT set_bit('\x00000000'::bytea, 0, 1);
Expected Output:
'\x00000001' or '\x80000000'
Actual Output:
'\x01000000'

Input:
SELECT set_bit('\x00000000'::bytea, 8, 1);
Expected Output:
'\x00000100' or '\x00800000'
Actual Output:
'\x00010000'

Issue:
set_bit function changes the right-most bit of the byte, but with
little-endian byte order. This is confusing to any use case where setting a
bit in a BYTEA in a specific position. To iterate through the bits within
the BYTEA, one must have nested loops which set bits within byte boundaries.


pgsql-bugs by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: BUG #16401: Minor misspelling for hint in Swedish
Next
From: Thomas Munro
Date:
Subject: Re: BUG #16402: No se puede instalar pgadmin4