agora inbox for pgsql-bugs@postgresql.org
help / color / mirror / Atom feedBUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-03 06:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-03 21:17 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-04 15:12 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-04 16:10 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-05 07:52 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-05 10:45 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-05 16:23 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-05 16:48 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col
2026-09-06 13:09 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[9+ messages in thread]
BUG #19654: JSON_EXISTS returns ON ERROR value for SQL NULL after a prior error
2026-09-04 09:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19654: JSON_EXISTS returns ON ERROR value for SQL NULL after a prior error
2026-09-04 10:12 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[2+ messages in thread]
BUG #19628: Uninterruptible vacuum during hash index processing
2026-08-18 12:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19628: Uninterruptible vacuum during hash index processing
2026-08-22 14:54 UTC mostafa nabil <mostafa.nabil.nafie@gmail.com>
` Re: BUG #19628: Uninterruptible vacuum during hash index processing
2026-09-03 06:48 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19628: Uninterruptible vacuum during hash index processing
2026-09-04 09:47 UTC mostafa nabil <mostafa.nabil.nafie@gmail.com>
[4+ messages in thread]
BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-08-18 03:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-08-18 13:29 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-08-19 02:28 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-08-19 07:02 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-08-25 19:23 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-08-25 20:02 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-09-04 03:11 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-09-04 06:38 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
2026-09-04 08:13 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[9+ messages in thread]
BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
2026-08-30 17:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
2026-09-02 18:51 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
2026-09-02 20:43 UTC Edwin Polkerman <edwin.polkerman@splendiddata.com>
` Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
2026-09-02 21:19 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
2026-09-03 11:55 UTC Edwin Polkerman <edwin.polkerman@splendiddata.com>
` Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
2026-09-03 16:49 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: BUG #19647: Difference in pg_basebackup behaviour between PostgreSQL <= 16 and >= 17 with pgactive extension
2026-09-03 19:35 UTC Edwin Polkerman <edwin.polkerman@splendiddata.com>
[7+ messages in thread]
BUG #19652: to_number() silently truncates over-length integers
2026-09-03 06:48 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19652: to_number() silently truncates over-length integers
2026-09-03 18:36 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[2+ messages in thread]
BUG #19651: to_date()/to_timestamp() silently accept out-of-range values for SSSSS, RM, IW and ID format fields
2026-09-03 06:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19651: to_date()/to_timestamp() silently accept out-of-range values for SSSSS, RM, IW and ID format fields
2026-09-03 15:36 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[2+ messages in thread]
BUG #19441: Backend waits for serializable snapshot indefinitely on removing temp relations
2026-03-29 10:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19441: Backend waits for serializable snapshot indefinitely on removing temp relations
2026-08-27 08:16 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19441: Backend waits for serializable snapshot indefinitely on removing temp relations
2026-08-27 08:49 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19441: Backend waits for serializable snapshot indefinitely on removing temp relations
2026-09-02 11:01 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19441: Backend waits for serializable snapshot indefinitely on removing temp relations
2026-09-02 11:44 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19441: Backend waits for serializable snapshot indefinitely on removing temp relations
2026-09-03 03:20 UTC Fujii Masao <masao.fujii@gmail.com>
[6+ messages in thread]
BUG #19645: Partition key opclass bypasses nondeterministic collation check, wrong results
2026-08-29 05:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19645: Partition key opclass bypasses nondeterministic collation check, wrong results
2026-09-02 06:28 UTC Zexin Li <lizi.openmind@gmail.com>
[2+ messages in thread]
BUG #19487: Error while executing SQL query involving XML parsing
2026-05-19 09:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-08-28 08:53 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-08-28 19:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-08-28 19:55 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-08-29 10:54 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-08-29 21:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-08-30 03:08 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-08-30 18:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-08-30 18:35 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-09-01 16:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19487: Error while executing SQL query involving XML parsing
2026-09-01 16:37 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[11+ messages in thread]
to_char() on integer with V format silently wraps on overflow
2026-08-13 12:01 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: to_char() on integer with V format silently wraps on overflow
2026-08-27 08:57 UTC Miłosz Bieniek <bieniek.milosz@proton.me>
` Re: to_char() on integer with V format silently wraps on overflow
2026-08-27 10:30 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: to_char() on integer with V format silently wraps on overflow
2026-08-27 21:26 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: to_char() on integer with V format silently wraps on overflow
2026-09-01 02:46 UTC Fujii Masao <masao.fujii@gmail.com>
[5+ messages in thread]
BUG #19648: Docs on DISTINCT ON do not describe how expressions are matched to ORDER BY
2026-08-31 23:10 UTC PG Bug reporting form <noreply@postgresql.org>
repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
2026-08-19 11:03 UTC Jochen Bandhauer <jb@jbitc.de>
` Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
2026-08-19 16:16 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
2026-08-25 19:57 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
2026-08-25 21:00 UTC Jochen Bandhauer <jb@jbitc.de>
` Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
2026-08-26 00:44 UTC Fujii Masao <masao.fujii@gmail.com>
` Fwd: Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
2026-08-26 07:18 UTC Jochen Bandhauer <jb@jbitc.de>
` Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
2026-08-26 12:56 UTC Jochen Bandhauer <jb@jbitc.de>
` Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
2026-08-31 11:20 UTC Jochen Bandhauer <jb@jbitc.de>
[8+ messages in thread]
BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-02 01:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-02 07:29 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-02 17:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-02 17:42 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-02 20:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-02 20:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-24 11:20 UTC Ewan Young <kdbase.hack@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-30 00:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-30 04:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-30 04:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-30 04:30 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-30 04:37 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-30 04:43 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-30 11:43 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19595: Three memory-safety defects in src/backend/tsearch/spell.c (dictionary loader), PG 18.3
2026-08-30 15:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
[15+ messages in thread]
BUG #19646: Unique index with explicit COLLATE bypasses nondeterministic collation rule
2026-08-29 05:39 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19643: Output of jsonb_populate_recordset not consistent with documentation description
2026-08-28 12:42 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19643: Output of jsonb_populate_recordset not consistent with documentation description
2026-08-28 13:28 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #19642: Include column name in error message when varchar(n) length limit is exceeded
2026-08-28 04:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19642: Include column name in error message when varchar(n) length limit is exceeded
2026-08-28 13:16 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #19498: Anonymous ROW() field expansion fails after scalar subquery relay
2026-05-27 11:50 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19498: Anonymous ROW() field expansion fails after scalar subquery relay
2026-08-27 21:20 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[2+ messages in thread]
MERGE/SPLIT PARTITIONS issues/questions
2026-07-23 11:59 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-07-23 14:29 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-01 09:49 UTC jian he <jian.universality@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-01 11:11 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-02 04:27 UTC jian he <jian.universality@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-02 06:56 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-03 19:26 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-05 01:27 UTC jian he <jian.universality@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-05 17:02 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-06 03:45 UTC jian he <jian.universality@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-06 22:59 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-11 21:36 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-12 20:38 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-12 20:48 UTC Melanie Plageman <melanieplageman@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-12 20:56 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-14 14:07 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-14 14:36 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-14 14:51 UTC Melanie Plageman <melanieplageman@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-14 15:49 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-17 10:27 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-17 10:31 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-17 10:35 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-18 03:47 UTC jian he <jian.universality@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-19 11:31 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-19 11:58 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-20 07:41 UTC jian he <jian.universality@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-20 11:46 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-21 09:36 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-21 13:48 UTC Melanie Plageman <melanieplageman@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-21 14:17 UTC Alexander Korotkov <aekorotkov@gmail.com>
` RE: MERGE/SPLIT PARTITIONS issues/questions
2026-08-23 06:37 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` RE: MERGE/SPLIT PARTITIONS issues/questions
2026-08-23 09:17 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-24 10:39 UTC jian he <jian.universality@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-24 22:16 UTC Robert Haas <robertmhaas@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-26 09:05 UTC jian he <jian.universality@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-26 16:37 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-26 16:42 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-26 23:39 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-27 20:24 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: MERGE/SPLIT PARTITIONS issues/questions
2026-08-27 20:40 UTC Robert Haas <robertmhaas@gmail.com>
[40+ messages in thread]
BUG #19640: Standby permanently stuck re-requesting old timeline after promotion, never switches to new timeline
2026-08-26 11:56 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19640: Standby permanently stuck re-requesting old timeline after promotion, never switches to new timeline
2026-08-27 16:17 UTC Andrey Borodin <x4mmm@yandex-team.ru>
[2+ messages in thread]
BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-02 22:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-08 04:15 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-08 06:52 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-12 21:16 UTC Si, Evan <evsi@amazon.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-13 16:59 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-13 19:06 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-13 19:11 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-14 18:15 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-14 18:18 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-14 20:26 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-14 21:07 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-15 07:32 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-15 20:27 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-01-23 18:22 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-08-26 14:38 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-08-26 22:02 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-08-26 23:28 UTC surya poondla <suryapoondla4@gmail.com>
` Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work
2026-08-27 15:49 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
[18+ messages in thread]
BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-19 03:50 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-19 15:22 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-19 16:12 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-20 09:06 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-20 22:30 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-21 05:18 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-21 08:41 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-24 12:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-24 23:49 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-25 05:14 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19629: pg_restore_relation_stats reports XX000 instead of proper SQLSTATE for input validation errors
2026-08-27 14:45 UTC Fujii Masao <masao.fujii@gmail.com>
[11+ messages in thread]
BUG #19637: pg_event_trigger_ddl_commands can't process GRANT ON PROPERTY GRAPH
2026-08-23 11:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19637: pg_event_trigger_ddl_commands can't process GRANT ON PROPERTY GRAPH
2026-08-24 13:30 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19637: pg_event_trigger_ddl_commands can't process GRANT ON PROPERTY GRAPH
2026-08-25 19:28 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19637: pg_event_trigger_ddl_commands can't process GRANT ON PROPERTY GRAPH
2026-08-25 20:01 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19637: pg_event_trigger_ddl_commands can't process GRANT ON PROPERTY GRAPH
2026-08-26 00:50 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: BUG #19637: pg_event_trigger_ddl_commands can't process GRANT ON PROPERTY GRAPH
2026-08-26 03:08 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19637: pg_event_trigger_ddl_commands can't process GRANT ON PROPERTY GRAPH
2026-08-27 09:59 UTC Peter Eisentraut <peter@eisentraut.org>
[7+ messages in thread]
Possible G2-item at SERIALIZABLE
2026-05-22 16:44 UTC Kyle Kingsbury <aphyr@aphyr.com>
` Re: Possible G2-item at SERIALIZABLE
2026-05-30 18:47 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
2026-05-31 13:19 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
2026-06-01 01:49 UTC Kyle Kingsbury <aphyr@jepsen.io>
` Re: Possible G2-item at SERIALIZABLE
2026-06-01 06:18 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
2026-06-01 10:11 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
2026-06-01 22:00 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Possible G2-item at SERIALIZABLE
2026-06-02 08:18 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
2026-06-02 23:03 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Possible G2-item at SERIALIZABLE
2026-06-17 17:39 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
2026-08-19 17:24 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Possible G2-item at SERIALIZABLE
2026-08-20 11:17 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: Possible G2-item at SERIALIZABLE
2026-08-26 21:33 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: Possible G2-item at SERIALIZABLE
2026-08-27 06:56 UTC Andrey Borodin <x4mmm@yandex-team.ru>
[14+ messages in thread]
SIGSEGV in dynahash
2026-08-15 13:06 UTC Konstantin Knizhnik <knizhnik@garret.ru>
` Re: SIGSEGV in dynahash
2026-08-15 16:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: SIGSEGV in dynahash
2026-08-15 23:32 UTC Michael Paquier <michael@paquier.xyz>
` Re: SIGSEGV in dynahash
2026-08-20 13:19 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: SIGSEGV in dynahash
2026-08-25 04:30 UTC Rahila Syed <rahilasyed90@gmail.com>
` Re: SIGSEGV in dynahash
2026-08-25 11:14 UTC Heikki Linnakangas <hlinnaka@iki.fi>
[6+ messages in thread]
[next (older)]
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox