CREATE UNLOGGED TABLE seq faults when debug_discard_caches=1

Hi Hackers, while testing the developer settings of PSQL (14.5) I came across this issue: postgres=# CREATE UNLOGGED TABLE stats ( postgres(# pg_hash BIGINT NOT NULL, postgres(# category TEXT NOT NULL, postgres(# PRIMARY KEY (pg_hash, category) postgres(# ); server closed the

Re: Bug: Reading from single byte character column type may cause out of bounds memory reads.

Hi all, this is to verify that the .patch proposed here: https://www.postgresql.org/message-id/flat/2318797.1638558730%40sss.pgh.pa.us fixes the issue. I applied the patch and: 1) The build type doesn't affect the result of the query result 2) The valgrind doesn't complain about out of bound

Bug: Reading from single byte character column type may cause out of bounds memory reads.

Hi hackers, While I was writing a test for PSQL, I faced a weird scenario. Depending on how I build PSQL (enabling or not debug options), I saw different results for the following query. Steps to reproduce: - OS: Ubuntu 20.04 - PSQL version 14.4 CREATE TABLE test (single_byte_col "char");