PostgreSQL Bugs

Collected from the PG bugs email list.

Bug ID16403
PG Version11.0
OSLinux
Opened2020-04-29 21:50:53+00
Reported byAlex Movitz
StatusNew

Body of first available message related to this bug follows.

The following bug has been logged on the website:

Bug reference:      16403
Logged by:          Alex Movitz
Email address:      (redacted)
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.

Messages

DateAuthorSubject
2020-04-29 21:50:53+00PG Bug reporting formBUG #16403: set_bit function does not have expected effect
2020-04-30 09:18:27+00Francisco OlarteRe: BUG #16403: set_bit function does not have expected effect
2020-04-30 13:57:46+00Tom LaneRe: BUG #16403: set_bit function does not have expected effect
2020-04-30 16:58:27+00Alex MovitzRe: BUG #16403: set_bit function does not have expected effect
2020-04-30 18:19:47+00Francisco OlarteRe: BUG #16403: set_bit function does not have expected effect