agora inbox for pgsql-committers@postgresql.orghelp / color / mirror / Atom feed
pgsql: amcheck: Use correct varlena size accessor in bt_normalize_tuple 6+ messages / 1 participants [nested] [flat]
* pgsql: amcheck: Use correct varlena size accessor in bt_normalize_tuple @ 2026-06-14 01:13 Alexander Korotkov <akorotkov@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Alexander Korotkov @ 2026-06-14 01:13 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org amcheck: Use correct varlena size accessor in bt_normalize_tuple() bt_normalize_tuple() uses VARSIZE() to get the size of varlena, even though it's not yet known, that it has a 4-byte header. Fix this by replacing a accessor with a universal VARSIZE_ANY(). Backpatch to all supported versions. Reported-by: Andres Freund <andres@anarazel.de> Discussion: https://postgr.es/m/7ckc7oka4bvafkf5bwlqs6ygrhlsbhz25ppozfch7zbuxcx3rf%40e4pr4oqenalc Author: Andrey Borodin <x4mmm@yandex-team.ru> Reviewed-by: Alexander Korotkov <aekorotkov@gmail.com> Backpatch-through: 14 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/da1eff08a5bedc4bea9f75c8412d877c5619afc0 Modified Files -------------- contrib/amcheck/verify_nbtree.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: amcheck: Use correct varlena size accessor in bt_normalize_tuple @ 2026-06-14 01:14 Alexander Korotkov <akorotkov@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Alexander Korotkov @ 2026-06-14 01:14 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org amcheck: Use correct varlena size accessor in bt_normalize_tuple() bt_normalize_tuple() uses VARSIZE() to get the size of varlena, even though it's not yet known, that it has a 4-byte header. Fix this by replacing a accessor with a universal VARSIZE_ANY(). Backpatch to all supported versions. Reported-by: Andres Freund <andres@anarazel.de> Discussion: https://postgr.es/m/7ckc7oka4bvafkf5bwlqs6ygrhlsbhz25ppozfch7zbuxcx3rf%40e4pr4oqenalc Author: Andrey Borodin <x4mmm@yandex-team.ru> Reviewed-by: Alexander Korotkov <aekorotkov@gmail.com> Backpatch-through: 14 Branch ------ REL_18_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/897e79486296d136855734a34de062eadfe3199b Modified Files -------------- contrib/amcheck/verify_nbtree.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: amcheck: Use correct varlena size accessor in bt_normalize_tuple @ 2026-06-14 01:14 Alexander Korotkov <akorotkov@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Alexander Korotkov @ 2026-06-14 01:14 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org amcheck: Use correct varlena size accessor in bt_normalize_tuple() bt_normalize_tuple() uses VARSIZE() to get the size of varlena, even though it's not yet known, that it has a 4-byte header. Fix this by replacing a accessor with a universal VARSIZE_ANY(). Backpatch to all supported versions. Reported-by: Andres Freund <andres@anarazel.de> Discussion: https://postgr.es/m/7ckc7oka4bvafkf5bwlqs6ygrhlsbhz25ppozfch7zbuxcx3rf%40e4pr4oqenalc Author: Andrey Borodin <x4mmm@yandex-team.ru> Reviewed-by: Alexander Korotkov <aekorotkov@gmail.com> Backpatch-through: 14 Branch ------ REL_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/8abb8a1555f4051491eced0307adf218e0f9f34e Modified Files -------------- contrib/amcheck/verify_nbtree.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: amcheck: Use correct varlena size accessor in bt_normalize_tuple @ 2026-06-14 01:14 Alexander Korotkov <akorotkov@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Alexander Korotkov @ 2026-06-14 01:14 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org amcheck: Use correct varlena size accessor in bt_normalize_tuple() bt_normalize_tuple() uses VARSIZE() to get the size of varlena, even though it's not yet known, that it has a 4-byte header. Fix this by replacing a accessor with a universal VARSIZE_ANY(). Backpatch to all supported versions. Reported-by: Andres Freund <andres@anarazel.de> Discussion: https://postgr.es/m/7ckc7oka4bvafkf5bwlqs6ygrhlsbhz25ppozfch7zbuxcx3rf%40e4pr4oqenalc Author: Andrey Borodin <x4mmm@yandex-team.ru> Reviewed-by: Alexander Korotkov <aekorotkov@gmail.com> Backpatch-through: 14 Branch ------ REL_16_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/c89a1ca01344b6015ab43904f88aef03ad965157 Modified Files -------------- contrib/amcheck/verify_nbtree.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: amcheck: Use correct varlena size accessor in bt_normalize_tuple @ 2026-06-14 01:14 Alexander Korotkov <akorotkov@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Alexander Korotkov @ 2026-06-14 01:14 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org amcheck: Use correct varlena size accessor in bt_normalize_tuple() bt_normalize_tuple() uses VARSIZE() to get the size of varlena, even though it's not yet known, that it has a 4-byte header. Fix this by replacing a accessor with a universal VARSIZE_ANY(). Backpatch to all supported versions. Reported-by: Andres Freund <andres@anarazel.de> Discussion: https://postgr.es/m/7ckc7oka4bvafkf5bwlqs6ygrhlsbhz25ppozfch7zbuxcx3rf%40e4pr4oqenalc Author: Andrey Borodin <x4mmm@yandex-team.ru> Reviewed-by: Alexander Korotkov <aekorotkov@gmail.com> Backpatch-through: 14 Branch ------ REL_15_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/4284476c0f67e9b3c4be36203193ca8ce8f21d40 Modified Files -------------- contrib/amcheck/verify_nbtree.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: amcheck: Use correct varlena size accessor in bt_normalize_tuple @ 2026-06-14 01:14 Alexander Korotkov <akorotkov@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Alexander Korotkov @ 2026-06-14 01:14 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org amcheck: Use correct varlena size accessor in bt_normalize_tuple() bt_normalize_tuple() uses VARSIZE() to get the size of varlena, even though it's not yet known, that it has a 4-byte header. Fix this by replacing a accessor with a universal VARSIZE_ANY(). Backpatch to all supported versions. Reported-by: Andres Freund <andres@anarazel.de> Discussion: https://postgr.es/m/7ckc7oka4bvafkf5bwlqs6ygrhlsbhz25ppozfch7zbuxcx3rf%40e4pr4oqenalc Author: Andrey Borodin <x4mmm@yandex-team.ru> Reviewed-by: Alexander Korotkov <aekorotkov@gmail.com> Backpatch-through: 14 Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/af09b18cbadbb91ffe617b9ee5549de420e9b21a Modified Files -------------- contrib/amcheck/verify_nbtree.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2026-06-14 01:14 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-06-14 01:13 pgsql: amcheck: Use correct varlena size accessor in bt_normalize_tuple Alexander Korotkov <akorotkov@postgresql.org> 2026-06-14 01:14 pgsql: amcheck: Use correct varlena size accessor in bt_normalize_tuple Alexander Korotkov <akorotkov@postgresql.org> 2026-06-14 01:14 pgsql: amcheck: Use correct varlena size accessor in bt_normalize_tuple Alexander Korotkov <akorotkov@postgresql.org> 2026-06-14 01:14 pgsql: amcheck: Use correct varlena size accessor in bt_normalize_tuple Alexander Korotkov <akorotkov@postgresql.org> 2026-06-14 01:14 pgsql: amcheck: Use correct varlena size accessor in bt_normalize_tuple Alexander Korotkov <akorotkov@postgresql.org> 2026-06-14 01:14 pgsql: amcheck: Use correct varlena size accessor in bt_normalize_tuple Alexander Korotkov <akorotkov@postgresql.org>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox