pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
2025-04-23 04:48 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
2025-04-23 11:03 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
2025-04-23 11:47 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
2025-04-24 08:40 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
2025-04-24 09:20 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
2025-04-24 09:43 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
2025-04-24 10:58 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
2025-04-24 13:29 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
2025-04-25 02:16 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
2025-04-27 00:14 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
2025-05-02 07:03 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
2025-05-03 01:50 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
2025-05-08 10:26 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18902: TRAP:: failed Assert("!is_sorted") in File: "createplan.c"
2025-05-08 10:28 UTC Richard Guo <guofenglinux@gmail.com>
[14+ messages in thread]
BUG #18917: "Foreign key constraint drop fails with 'column is not in index' unless pg_constraint is queried
2025-05-08 01:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18917: "Foreign key constraint drop fails with 'column is not in index' unless pg_constraint is queried
2025-05-08 01:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18916: alter table ... set (n_distinct=) completely ignored on partition head and/or individual partitions
2025-05-07 21:18 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18916: alter table ... set (n_distinct=) completely ignored on partition head and/or individual partitions
2025-05-07 22:49 UTC David Rowley <dgrowleyml@gmail.com>
[2+ messages in thread]
Different behavior between v15 and v17 using WITH CTE
2025-05-07 18:58 UTC marcos sicat <marcos.sicat@atlasifs.com>
` Re: Different behavior between v15 and v17 using WITH CTE
2025-05-07 19:03 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Different behavior between v15 and v17 using WITH CTE
2025-05-07 19:07 UTC marcos sicat <marcos.sicat@atlasifs.com>
[3+ messages in thread]
BUG #18913: pgdg-redhat-repo-42.0-52PGDG.noarch: Cannot download, all mirrors were already tried without succes
2025-05-07 02:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18913: pgdg-redhat-repo-42.0-52PGDG.noarch: Cannot download, all mirrors were already tried without succes
2025-05-07 16:26 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #18915: pgdg-redhat-repo-42.0-51PGDG.noarch package not available in postgres repo
2025-05-07 13:14 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18915: pgdg-redhat-repo-42.0-51PGDG.noarch package not available in postgres repo
2025-05-07 16:25 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #18914: REDUNDANT_COMPARISON.ALWAYS_FALSE Redundant comparison '0' > 'nb' (0 > {4, 16}) is always false
2025-05-07 08:48 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18914: REDUNDANT_COMPARISON.ALWAYS_FALSE Redundant comparison '0' > 'nb' (0 > {4, 16}) is always false
2025-05-07 10:34 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18914: REDUNDANT_COMPARISON.ALWAYS_FALSE Redundant comparison '0' > 'nb' (0 > {4, 16}) is always false
2025-05-07 10:35 UTC Daniel Gustafsson <daniel@yesql.se>
[3+ messages in thread]
BUG #18912: TRAP: failed Assert("tag.spcOid != GLOBALTABLESPACE_OID"), File: "bufmgr.c", Line: 4165, PID: 2115
2025-05-05 22:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18912: TRAP: failed Assert("tag.spcOid != GLOBALTABLESPACE_OID"), File: "bufmgr.c", Line: 4165, PID: 2115
2025-05-06 00:31 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #18912: TRAP: failed Assert("tag.spcOid != GLOBALTABLESPACE_OID"), File: "bufmgr.c", Line: 4165, PID: 2115
2025-05-06 04:52 UTC Masahiko Sawada <sawada.mshk@gmail.com>
[3+ messages in thread]
BUG #18910: DEREF_OF_NULL.RET Pointer, returned from function 'palloc0' at simplehash.h:1080, may be NULL
2025-05-05 08:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18910: DEREF_OF_NULL.RET Pointer, returned from function 'palloc0' at simplehash.h:1080, may be NULL
2025-05-05 14:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18909: Query creates millions of temporary files and stalls
2025-05-02 18:45 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18909: Query creates millions of temporary files and stalls
2025-05-02 22:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18909: Query creates millions of temporary files and stalls
2025-05-02 22:44 UTC Sergey Koposov <Sergey.Koposov@ed.ac.uk>
` Re: BUG #18909: Query creates millions of temporary files and stalls
2025-05-03 16:11 UTC Sergey Koposov <Sergey.Koposov@ed.ac.uk>
` Re: BUG #18909: Query creates millions of temporary files and stalls
2025-05-03 16:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18909: Query creates millions of temporary files and stalls
2025-05-03 16:52 UTC Sergey Koposov <Sergey.Koposov@ed.ac.uk>
` Re: BUG #18909: Query creates millions of temporary files and stalls
2025-05-03 17:56 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18909: Query creates millions of temporary files and stalls
2025-05-03 19:20 UTC Sergey Koposov <Sergey.Koposov@ed.ac.uk>
` Re: BUG #18909: Query creates millions of temporary files and stalls
2025-05-03 21:50 UTC Sergey Koposov <Sergey.Koposov@ed.ac.uk>
` Re: BUG #18909: Query creates millions of temporary files and stalls
2025-05-03 22:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18909: Query creates millions of temporary files and stalls
2025-05-03 22:30 UTC Sergey Koposov <Sergey.Koposov@ed.ac.uk>
` Re: BUG #18909: Query creates millions of temporary files and stalls
2025-05-03 22:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18909: Query creates millions of temporary files and stalls
2025-05-03 23:05 UTC Sergey Koposov <Sergey.Koposov@ed.ac.uk>
` Re: BUG #18909: Query creates millions of temporary files and stalls
2025-05-04 07:52 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18909: Query creates millions of temporary files and stalls
2025-05-04 11:45 UTC Sergey Koposov <Sergey.Koposov@ed.ac.uk>
` Re: BUG #18909: Query creates millions of temporary files and stalls
2025-05-04 12:13 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18909: Query creates millions of temporary files and stalls
2025-05-04 12:35 UTC Sergey Koposov <Sergey.Koposov@ed.ac.uk>
[17+ messages in thread]
Planner does not use btree index for LIKE 'prefix%' on text column, but does for equivalent range query (PostgreSQL 17.4)
2025-05-03 16:50 UTC Abdullah DURSUN <adursuns@gmail.com>
` Re: Planner does not use btree index for LIKE 'prefix%' on text column, but does for equivalent range query (PostgreSQL 17.4)
2025-05-03 20:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error
2024-12-08 12:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error
2024-12-09 02:56 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error
2024-12-31 05:00 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error
2025-05-03 01:22 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18741: Detaching a partition referencing a partitioned table fails with a trigger-related error
2025-05-03 05:00 UTC Alexander Lakhin <exclusion@gmail.com>
[5+ messages in thread]
[PATCH] Fix self-referencing foreign keys on partitioned tables
2025-05-01 11:14 UTC Álvaro Herrera <alvherre@kurilemu.de>
Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-27 20:51 UTC marcos sicat <marcos.sicat@atlasifs.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-28 06:17 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-28 13:05 UTC marcos sicat <marcos.sicat@atlasifs.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-28 13:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-28 21:53 UTC marcos sicat <marcos.sicat@atlasifs.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-29 05:00 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-30 21:43 UTC marcos sicat <marcos.sicat@atlasifs.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-30 23:16 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-04-30 23:53 UTC marcos sicat <marcos.sicat@atlasifs.com>
` Re: Postgres 17.4 is much slower than Postgres 15.12 using RECURSIVE
2025-05-01 00:27 UTC marcos sicat <marcos.sicat@atlasifs.com>
[10+ messages in thread]
Doubt in reset date style
2025-04-30 21:17 UTC Manav Kumar <mkumar@yugabyte.com>
` Re: Doubt in reset date style
2025-04-30 21:31 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Doubt in reset date style
2025-04-30 21:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #17695: Failed Assert in logical replication snapbuild.
2022-11-24 10:15 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2022-11-24 12:39 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2022-11-25 05:58 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2022-11-25 07:44 UTC bowenshi <zxwsbg@qq.com>
` RE: BUG #17695: Failed Assert in logical replication snapbuild.
2022-11-25 09:07 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2022-11-25 09:56 UTC bowenshi <zxwsbg@qq.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2022-11-28 05:07 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2023-03-27 11:49 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2023-05-17 05:34 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2023-05-18 14:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2023-05-22 00:56 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2023-05-23 11:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2023-07-04 15:43 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2023-07-05 01:23 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2023-09-19 08:15 UTC Alexander Pyhalov <a.pyhalov@postgrespro.ru>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2025-04-30 18:19 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17695: Failed Assert in logical replication snapbuild.
2025-04-30 19:55 UTC Masahiko Sawada <sawada.mshk@gmail.com>
[17+ messages in thread]
BUG #18904: INTERSECT with an impossible where should eliminate both from the query plan
2025-04-27 16:15 UTC PG Bug reporting form <noreply@postgresql.org>
` BUG #18904: INTERSECT with an impossible where should eliminate both from the query plan
2025-04-27 17:32 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18904: INTERSECT with an impossible where should eliminate both from the query plan
2025-04-27 18:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18904: INTERSECT with an impossible where should eliminate both from the query plan
2025-04-29 11:57 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18904: INTERSECT with an impossible where should eliminateboth from the query plan
2025-04-29 12:13 UTC =?utf-8?B?SmluaHVpIExhaQ==?= <jh.lai@qq.com>
` Re: BUG #18904: INTERSECT with an impossible where should eliminateboth from the query plan
2025-04-29 12:55 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18904: INTERSECT with an impossible where should eliminateboth from the query plan
2025-04-29 18:44 UTC Francisco Olarte <folarte@peoplecall.com>
[7+ messages in thread]
BUG #18905: The opposite WHERE clause intersects and is always an empty set. It should perform no action.
2025-04-27 16:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18905: The opposite WHERE clause intersects and is always an empty set. It should perform no action.
2025-04-27 17:34 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18905: The opposite WHERE clause intersects and is always an empty set. It should perform no action.
2025-04-27 17:54 UTC =?utf-8?B?6LWW6ZSm6L6J?= <jh.lai@qq.com>
` Re: BUG #18905: The opposite WHERE clause intersects and is always an empty set. It should perform no action.
2025-04-27 19:19 UTC Christophe Pettus <xof@thebuild.com>
[4+ messages in thread]
BUG #18906: EXCEPT with identical left/right queries isn't eliminated
2025-04-27 17:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18906: EXCEPT with identical left/right queries isn't eliminated
2025-04-27 17:37 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18903: TRAP: failed Assert("false") in file: "tuplesortvariants.c"
2025-04-25 05:20 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18903: TRAP: failed Assert("false") in file: "tuplesortvariants.c"
2025-04-25 06:51 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18903: TRAP: failed Assert("false") in file: "tuplesortvariants.c"
2025-04-25 07:00 UTC Никита Калинин <n.kalinin@postgrespro.ru>
` Re: BUG #18903: TRAP: failed Assert("false") in file: "tuplesortvariants.c"
2025-04-25 07:15 UTC Dilip Kumar <dilipbalaut@gmail.com>
[4+ messages in thread]
BUG #18893: Segfault during analyze pg_database
2025-04-12 03:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18893: Segfault during analyze pg_database
2025-04-13 12:11 UTC Robins Tharakan <tharakan@gmail.com>
` Re: BUG #18893: Segfault during analyze pg_database
2025-04-13 14:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18893: Segfault during analyze pg_database
2025-04-14 09:18 UTC Robins Tharakan <tharakan@gmail.com>
` Re: BUG #18893: Segfault during analyze pg_database
2025-04-24 23:31 UTC Michael Paquier <michael@paquier.xyz>
[5+ messages in thread]
DSA refcnt overflow in pg_stat/could not attach to dynamic shared area
2025-04-24 06:04 UTC =?gb18030?B?wO7UsNSw?= <summer.li.yuan@qq.com>
` Re: DSA refcnt overflow in pg_stat/could not attach to dynamic shared area
2025-04-24 07:05 UTC Michael Paquier <michael@paquier.xyz>
[2+ messages in thread]
Disabled logical replication origin session causes primary key errors
2025-04-18 21:22 UTC Shawn McCoy <shawn.the.mccoy@gmail.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-20 05:53 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-21 05:17 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: Disabled logical replication origin session causes primary key errors
2025-04-21 10:08 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-21 16:17 UTC vignesh C <vignesh21@gmail.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-21 17:00 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-22 02:35 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: Disabled logical replication origin session causes primary key errors
2025-04-22 09:06 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-22 09:36 UTC vignesh C <vignesh21@gmail.com>
` RE: Disabled logical replication origin session causes primary key errors
2025-04-22 11:00 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-22 13:37 UTC vignesh C <vignesh21@gmail.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-22 18:10 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-22 20:10 UTC Shawn McCoy <shawn.the.mccoy@gmail.com>
` RE: Disabled logical replication origin session causes primary key errors
2025-04-23 01:41 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-23 09:01 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-23 15:58 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Disabled logical replication origin session causes primary key errors
2025-04-24 02:25 UTC Michael Paquier <michael@paquier.xyz>
[17+ messages in thread]
Command order bug in pg_dump
2025-04-21 10:56 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Command order bug in pg_dump
2025-04-21 14:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Command order bug in pg_dump
2025-04-21 17:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Command order bug in pg_dump
2025-04-21 17:30 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Command order bug in pg_dump
2025-04-21 17:33 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Command order bug in pg_dump
2025-04-21 17:44 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Command order bug in pg_dump
2025-04-21 19:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Command order bug in pg_dump
2025-04-22 19:08 UTC Alvaro Herrera <alvherre@kurilemu.de>
` Re: Command order bug in pg_dump
2025-04-22 19:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Command order bug in pg_dump
2025-04-22 20:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Command order bug in pg_dump
2025-04-23 02:59 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Command order bug in pg_dump
2025-04-23 13:01 UTC Alvaro Herrera <alvherre@kurilemu.de>
` Re: Command order bug in pg_dump
2025-04-23 14:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
[13+ messages in thread]
BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-09 13:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-09 22:47 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-10 12:28 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-11 22:30 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-13 23:26 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-14 14:41 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-15 09:41 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-15 13:16 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-16 04:11 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-16 06:57 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-16 10:00 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-21 09:41 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-21 12:11 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-21 20:23 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2
2025-04-23 06:52 UTC Andrei Lepikhov <lepihov@gmail.com>
[15+ messages in thread]
[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