pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #19636: heap_fill_tuple misses short varlena conversion after EOH_flatten_into, causing 3-byte waste per row
2026-08-21 09:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19636: heap_fill_tuple misses short varlena conversion after EOH_flatten_into, causing 3-byte waste per row
2026-08-21 14:37 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19636: heap_fill_tuple misses short varlena conversion after EOH_flatten_into, causing 3-byte waste per row
2026-08-21 22:07 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[3+ messages in thread]
BUG #19634: Hash partition with large MODULUS causes "invalid memory alloc request size"
2026-08-21 03:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19634: Hash partition with large MODULUS causes "invalid memory alloc request size"
2026-08-21 12:04 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: BUG #19634: Hash partition with large MODULUS causes "invalid memory alloc request size"
2026-08-21 12:24 UTC Andres Freund <andres@anarazel.de>
[3+ messages in thread]
BUG #19630: FOR PORTION OF crashes with XX000 when target range is NULL
2026-08-19 03:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19630: FOR PORTION OF crashes with XX000 when target range is NULL
2026-08-19 11:11 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: BUG #19630: FOR PORTION OF crashes with XX000 when target range is NULL
2026-08-21 12:16 UTC Peter Eisentraut <peter@eisentraut.org>
[3+ messages in thread]
BUG #19635: Missing entry in information_schema.sequences when creating a Tale with auto increment
2026-08-21 09:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19635: Missing entry in information_schema.sequences when creating a Tale with auto increment
2026-08-21 12:00 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[2+ messages in thread]
BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-19 03:52 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-19 10:10 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-19 10:56 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-19 23:37 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-20 08:29 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-20 08:58 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-20 22:14 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-20 22:53 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19632: RULE rewriting crashes with XX000 when RETURNING old/new references a system column
2026-08-21 11:34 UTC Álvaro Herrera <alvherre@kurilemu.de>
[9+ messages in thread]
BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-02 17:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-04 08:54 UTC Zexin Li <lizi.openmind@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-05 06:03 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-07 01:58 UTC Zexin Li <lizi.openmind@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-10 05:47 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-10 08:23 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-11 00:40 UTC Zexin Li <lizi.openmind@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-12 08:09 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-14 06:33 UTC Zexin Li <lizi.openmind@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-14 14:08 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-17 03:23 UTC Zexin Li <lizi.openmind@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-19 17:57 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
2026-08-21 07:55 UTC Fujii Masao <masao.fujii@gmail.com>
[13+ messages in thread]
pg_restore: stack-buffer-overflow(read) in _tarGetHeader() in pg_backup_tar.c
2026-08-20 13:22 UTC Ilia Kashintsev <ilia.kashintsev@gmail.com>
BUG #19623: Postmaster livelocks respawning io workers when children die after crash restart; pg_ctl stop fails
2026-08-17 04:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19623: Postmaster livelocks respawning io workers when children die after crash restart; pg_ctl stop fails
2026-08-20 01:28 UTC Zexin Li <lizi.openmind@gmail.com>
` Re: BUG #19623: Postmaster livelocks respawning io workers when children die after crash restart; pg_ctl stop fails
2026-08-20 01:44 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19623: Postmaster livelocks respawning io workers when children die after crash restart; pg_ctl stop fails
2026-08-20 02:21 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19623: Postmaster livelocks respawning io workers when children die after crash restart; pg_ctl stop fails
2026-08-20 07:06 UTC Michael Paquier <michael@paquier.xyz>
[5+ messages in thread]
BUG #19627: 32,768 trigger arguments wrap `tgnargs` and are silently lost at runtime
2026-08-18 09:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19627: 32,768 trigger arguments wrap `tgnargs` and are silently lost at runtime
2026-08-19 02:56 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #19627: 32,768 trigger arguments wrap `tgnargs` and are silently lost at runtime
2026-08-19 05:22 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19627: 32,768 trigger arguments wrap `tgnargs` and are silently lost at runtime
2026-08-20 00:40 UTC Michael Paquier <michael@paquier.xyz>
[4+ messages in thread]
[PATCH v1] Reject too many arguments in CREATE TRIGGER
2026-08-19 02:40 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` [PATCH v1] Reject too many arguments in CREATE TRIGGER
2026-08-19 02:40 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
[2+ messages in thread]
B-tree index scan ~2x slower on PG18 vs PG17 for skewed equality-prefix + range-condition lookups, with essentially the same plan
2026-08-17 21:45 UTC Dan Stefura <dstefura@bluecatnetworks.com>
` Re: B-tree index scan ~2x slower on PG18 vs PG17 for skewed equality-prefix + range-condition lookups, with essentially the same plan
2026-08-18 16:24 UTC Peter Geoghegan <pg@bowt.ie>
` Re: B-tree index scan ~2x slower on PG18 vs PG17 for skewed equality-prefix + range-condition lookups, with essentially the same plan
2026-08-18 19:53 UTC Dan Stefura <dstefura@bluecatnetworks.com>
[3+ messages in thread]
BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming
2026-08-11 22:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming
2026-08-13 17:56 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming
2026-08-13 23:03 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` RE: BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming
2026-08-14 03:03 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming
2026-08-14 04:56 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` RE: BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming
2026-08-14 06:10 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming
2026-08-14 06:44 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` RE: BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming
2026-08-14 10:09 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming
2026-08-14 12:33 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming
2026-08-14 14:34 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming
2026-08-14 22:15 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming
2026-08-15 02:27 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming
2026-08-17 20:46 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming
2026-08-18 08:29 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming
2026-08-18 19:00 UTC Masahiko Sawada <sawada.mshk@gmail.com>
[15+ messages in thread]
BUG #19624: postgresql14-devel (and in general postgresqlXX-devel) do not set PKG_CONFIG_PATH
2026-08-17 12:50 UTC PG Bug reporting form <noreply@postgresql.org>
Autovacuum and vacuum spoil reltuples statistics on nontruncated relation
2026-08-17 10:13 UTC Oleg Gurev <gurevoleg@gmail.com>
BUG #19583: macaddr input accepts octet fields longer than 8 hex digits
2026-07-29 00:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19583: macaddr input accepts octet fields longer than 8 hex digits
2026-07-29 12:47 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19583: macaddr input accepts octet fields longer than 8 hex digits
2026-08-01 01:40 UTC Zexin Li <lizi.openmind@gmail.com>
` Re: BUG #19583: macaddr input accepts octet fields longer than 8 hex digits
2026-08-01 19:16 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19583: macaddr input accepts octet fields longer than 8 hex digits
2026-08-04 01:04 UTC Zexin Li <lizi.openmind@gmail.com>
` Re: BUG #19583: macaddr input accepts octet fields longer than 8 hex digits
2026-08-16 23:36 UTC Zexin Li <lizi.openmind@gmail.com>
[6+ messages in thread]
BUG #19612: SEGV in ParseConfigFp() in guc-file.l
2026-08-07 13:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19612: SEGV in ParseConfigFp() in guc-file.l
2026-08-11 06:30 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19612: SEGV in ParseConfigFp() in guc-file.l
2026-08-13 08:27 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19612: SEGV in ParseConfigFp() in guc-file.l
2026-08-13 09:00 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19612: SEGV in ParseConfigFp() in guc-file.l
2026-08-16 06:05 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19612: SEGV in ParseConfigFp() in guc-file.l
2026-08-16 06:50 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19612: SEGV in ParseConfigFp() in guc-file.l
2026-08-16 14:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19612: SEGV in ParseConfigFp() in guc-file.l
2026-08-16 22:26 UTC Michael Paquier <michael@paquier.xyz>
[8+ messages in thread]
BUG #19613: pg_restore: several SEGVs in ReadToc() in pg_backup_archiver.c
2026-08-07 13:37 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19613: pg_restore: several SEGVs in ReadToc() in pg_backup_archiver.c
2026-08-11 07:05 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19613: pg_restore: several SEGVs in ReadToc() in pg_backup_archiver.c
2026-08-14 11:58 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19613: pg_restore: several SEGVs in ReadToc() in pg_backup_archiver.c
2026-08-14 13:59 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19613: pg_restore: several SEGVs in ReadToc() in pg_backup_archiver.c
2026-08-14 16:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19613: pg_restore: several SEGVs in ReadToc() in pg_backup_archiver.c
2026-08-14 18:02 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19613: pg_restore: several SEGVs in ReadToc() in pg_backup_archiver.c
2026-08-16 15:03 UTC Andrey Borodin <x4mmm@yandex-team.ru>
[7+ messages in thread]
Should CUSTER (ANALYZE) work?
2026-07-21 21:36 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Should CUSTER (ANALYZE) work?
2026-08-12 19:50 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Should CUSTER (ANALYZE) work?
2026-08-13 20:38 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Should CUSTER (ANALYZE) work?
2026-08-15 09:12 UTC Alvaro Herrera <alvherre@kurilemu.de>
[4+ messages in thread]
BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-02 13:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-02 13:54 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-02 14:06 UTC =?windows-1250?Q?Adrian_M=F6nnich?= <adrian.moennich@cern.ch>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-02 14:27 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-02 14:49 UTC Adrian Mönnich <adrian.moennich@cern.ch>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-02 18:12 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-02 19:00 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-02 22:34 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-02 22:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-04 14:45 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-16 05:25 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-04-16 18:52 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-05-19 10:10 UTC Adrian Mönnich <adrian.moennich@cern.ch>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-08-14 15:10 UTC Adrian Mönnich <adrian.moennich@cern.ch>
` Re: BUG #19449: Massive performance degradation for complex query on Postgres 16+ (few seconds -> multiple hours)
2026-08-14 19:11 UTC Tomas Vondra <tomas@vondra.me>
[15+ messages in thread]
BUG #19619: WHERE scale(n) = 1 pushed past GROUP BY / window PARTITION BY, wrong COUNT
2026-08-14 17:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19619: WHERE scale(n) = 1 pushed past GROUP BY / window PARTITION BY, wrong COUNT
2026-08-14 18:30 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19619: WHERE scale(n) = 1 pushed past GROUP BY / window PARTITION BY, wrong COUNT
2026-08-14 18:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
COPY TO regression with psql -c
2026-08-11 19:32 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: COPY TO regression with psql -c
2026-08-12 08:37 UTC Christoph Berg <myon@debian.org>
` Re: COPY TO regression with psql -c
2026-08-12 17:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: COPY TO regression with psql -c
2026-08-12 19:53 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: COPY TO regression with psql -c
2026-08-13 20:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: COPY TO regression with psql -c
2026-08-13 22:52 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: COPY TO regression with psql -c
2026-08-14 16:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
[7+ messages in thread]
DELETE FOR PORTION OF bypasses view WITH CHECK OPTION for leftover rows
2026-07-22 18:43 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: DELETE FOR PORTION OF bypasses view WITH CHECK OPTION for leftover rows
2026-07-29 05:30 UTC solai v <solai.cdac@gmail.com>
` Re: DELETE FOR PORTION OF bypasses view WITH CHECK OPTION for leftover rows
2026-08-12 21:30 UTC Melanie Plageman <melanieplageman@gmail.com>
` Re: DELETE FOR PORTION OF bypasses view WITH CHECK OPTION for leftover rows
2026-08-12 23:18 UTC Paul A Jungwirth <pj@illuminatedcomputing.com>
` Re: DELETE FOR PORTION OF bypasses view WITH CHECK OPTION for leftover rows
2026-08-13 09:23 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: DELETE FOR PORTION OF bypasses view WITH CHECK OPTION for leftover rows
2026-08-14 12:01 UTC Peter Eisentraut <peter@eisentraut.org>
[6+ messages in thread]
BUG #19617: Hash node can report incorrect actual rows number
2026-08-12 23:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19617: Hash node can report incorrect actual rows number
2026-08-13 17:36 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
[2+ messages in thread]
pg_upgrade from 17.10 to 18.4 on Ubuntu fails: Finding the real data directory for the target cluster sh: 1: (null)/postgres: not found
2026-08-12 10:50 UTC Holger Jakobs <holger@jakobs.com>
` Re: pg_upgrade from 17.10 to 18.4 on Ubuntu fails: Finding the real data directory for the target cluster sh: 1: (null)/postgres: not found
2026-08-12 15:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_upgrade from 17.10 to 18.4 on Ubuntu fails: Finding the real data directory for the target cluster sh: 1: (null)/postgres: not found
2026-08-13 12:37 UTC Michael Banck <mbanck@gmx.net>
[3+ messages in thread]
BUG #19618: postgresql18 client package not found
2026-08-13 10:47 UTC PG Bug reporting form <noreply@postgresql.org>
[next (older)]
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox