pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #19049: Assert failure when using skip arrays on an index key with DESC order
2025-09-11 12:38 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19049: Assert failure when using skip arrays on an index key with DESC order
2025-09-11 15:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19049: Assert failure when using skip arrays on an index key with DESC order
2025-09-11 15:51 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #19049: Assert failure when using skip arrays on an index key with DESC order
2025-09-11 16:48 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #19049: Assert failure when using skip arrays on an index key with DESC order
2025-09-11 17:08 UTC Natalya Aksman <natalya@tigerdata.com>
` Re: BUG #19049: Assert failure when using skip arrays on an index key with DESC order
2025-09-11 17:16 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #19049: Assert failure when using skip arrays on an index key with DESC order
2025-09-12 01:07 UTC Peter Geoghegan <pg@bowt.ie>
[7+ messages in thread]
BUG #19045: Applying custom collation rules appears to erase existing rules
2025-09-09 15:13 UTC PG Bug reporting form <noreply@postgresql.org>
` RE: BUG #19045: Applying custom collation rules appears to erase existing rules
2025-09-11 18:14 UTC Todd Lang <Todd.Lang@D2L.com>
` RE: BUG #19045: Applying custom collation rules appears to erase existing rules
2025-09-11 18:38 UTC Todd Lang <Todd.Lang@D2L.com>
[3+ messages in thread]
BUG #19047: pg_last_wal_replay_lsn() returns non-NULL after pg_promote()
2025-09-11 07:09 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19047: pg_last_wal_replay_lsn() returns non-NULL after pg_promote()
2025-09-11 14:47 UTC Dilip Kumar <dilipbalaut@gmail.com>
[2+ messages in thread]
BUG #18760: ../doc/src/sgml/postgres.sgml:24: element book: validity error : No declaration for attribute id of
2024-12-31 09:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18760: ../doc/src/sgml/postgres.sgml:24: element book: validity error : No declaration for attribute id of
2025-03-20 01:32 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18760: ../doc/src/sgml/postgres.sgml:24: element book: validity error : No declaration for attribute id of
2025-03-20 03:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18760: ../doc/src/sgml/postgres.sgml:24: element book: validity error : No declaration for attribute id of
2025-09-11 14:34 UTC Andrey Teplitskiy <a.teplitskiy@postgrespro.ru>
[4+ messages in thread]
PostgreSQL Windows Turkish Search Problem
2025-09-11 07:42 UTC =?iso-8859-9?Q?Halil_=DDbrahim_AYHAN?= <ibrahimayhan@hotmail.com.tr>
` Re: PostgreSQL Windows Turkish Search Problem
2025-09-11 13:24 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
BUG #19048: PostgreSQL Windows Turkish Search Problem
2025-09-11 07:43 UTC PG Bug reporting form <noreply@postgresql.org>
PostgreSQL fails to start inside Nix' darwin sandbox
2025-09-09 09:33 UTC Wolfgang Walther <walther@technowledgy.de>
` Re: PostgreSQL fails to start inside Nix' darwin sandbox
2025-09-10 22:45 UTC Thomas Munro <thomas.munro@gmail.com>
[2+ messages in thread]
BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-02 15:58 UTC PG Bug reporting form <noreply@postgresql.org>
` 回复：BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-03 00:06 UTC =?UTF-8?B?5p2O5rW35rSLKOmZjOeXlSk=?= <mohen.lhy@alibaba-inc.com>
` Re:BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-03 01:43 UTC ocean_li_996 <ocean_li_996@163.com>
` Re: BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-03 02:20 UTC feichanghong <feichanghong@qq.com>
` Re: BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-03 15:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` 回复：BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-05 05:13 UTC =?UTF-8?B?5p2O5rW35rSLKOmZjOeXlSk=?= <mohen.lhy@alibaba-inc.com>
` Re: 回复：BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-06 20:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` 回复：回复：BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-07 08:24 UTC =?UTF-8?B?5p2O5rW35rSLKOmZjOeXlSk=?= <mohen.lhy@alibaba-inc.com>
` Re: BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-07 09:02 UTC feichanghong <feichanghong@qq.com>
` Re: BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-08 17:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-08 20:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
` 回复：BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-09 01:52 UTC =?UTF-8?B?5p2O5rW35rSLKOmZjOeXlSk=?= <mohen.lhy@alibaba-inc.com>
` Re: BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-09 02:51 UTC feichanghong <feichanghong@qq.com>
` Re: BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-09 03:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` 回复：BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-09 07:30 UTC =?UTF-8?B?5p2O5rW35rSLKOmZjOeXlSk=?= <mohen.lhy@alibaba-inc.com>
` Re: 回复：BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-09 22:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` 回复：回复：BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-10 01:55 UTC =?UTF-8?B?5p2O5rW35rSLKOmZjOeXlSk=?= <mohen.lhy@alibaba-inc.com>
` Re: BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-10 02:32 UTC feichanghong <feichanghong@qq.com>
` Re: BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-10 20:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
[19+ messages in thread]
BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-08-28 12:09 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-04 09:03 UTC Yushu Chen <gentcys@gmail.com>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-04 15:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-05 12:17 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-05 12:55 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-05 14:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-07 15:34 UTC Katja Henke <katja.henke@foo.ag>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-07 21:09 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-07 21:58 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-07 22:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-07 22:50 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-08 08:31 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
2025-09-08 15:10 UTC David G. Johnston <david.g.johnston@gmail.com>
[13+ messages in thread]
AW: BUG #19043: jdbc connection url is not case insensitive
2025-09-08 06:39 UTC Kristo Marijo <M.Kristo@rewe-group.at>
Broken PQtrace CopyData display
2025-08-29 19:45 UTC Ran Benita <ran@unusedvar.com>
` Re: Broken PQtrace CopyData display
2025-08-31 04:53 UTC Michael Paquier <michael@paquier.xyz>
` Re: Broken PQtrace CopyData display
2025-09-03 03:58 UTC Michael Paquier <michael@paquier.xyz>
` Re: Broken PQtrace CopyData display
2025-09-06 08:42 UTC Álvaro Herrera <alvherre@kurilemu.de>
[4+ messages in thread]
BUG #19043: jdbc connection url is not case insensitive
2025-09-05 06:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19043: jdbc connection url is not case insensitive
2025-09-05 21:13 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19043: jdbc connection url is not case insensitive
2025-09-05 21:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19043: jdbc connection url is not case insensitive
2025-09-06 00:41 UTC Greg Sabino Mullane <htamfids@gmail.com>
[4+ messages in thread]
BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-08-30 12:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-08-30 21:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-01 07:32 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-01 14:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-02 06:49 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-02 15:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-03 00:42 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-03 01:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-03 08:08 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-03 08:56 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error
2025-09-05 04:00 UTC Alexander Lakhin <exclusion@gmail.com>
[11+ messages in thread]
BUG #19041: Logical replication locks wal processing
2025-09-03 10:19 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19041: Logical replication locks wal processing
2025-09-03 11:55 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19041: Logical replication locks wal processing
2025-09-03 12:10 UTC Sergey Belyashov <sergey.belyashov@gmail.com>
` Re: BUG #19041: Logical replication locks wal processing
2025-09-03 12:45 UTC Dilip Kumar <dilipbalaut@gmail.com>
` RE: BUG #19041: Logical replication locks wal processing
2025-09-05 02:28 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
[5+ messages in thread]
empty,query_id, pg_stat_activity
2025-09-02 09:25 UTC zhouenbing <zhouenbing@sunwoda-evb.com>
` Re: empty,query_id, pg_stat_activity
2025-09-02 15:11 UTC Greg Sabino Mullane <htamfids@gmail.com>
` 答复: empty,query_id, pg_stat_activity
2025-09-03 02:00 UTC zhouenbing <zhouenbing@sunwoda-evb.com>
` Re: empty,query_id, pg_stat_activity
2025-09-03 20:54 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: empty,query_id, pg_stat_activity
2025-09-04 00:25 UTC Michael Paquier <michael@paquier.xyz>
` Re: empty,query_id, pg_stat_activity
2025-09-04 12:56 UTC Greg Sabino Mullane <htamfids@gmail.com>
[6+ messages in thread]
Postgres immediately closing connection when `systemctl reboot` command is fired.
2025-09-04 08:59 UTC Raghvendra Mishra <raghshr1351@gmail.com>
=?gb2312?B?tPC4tDogZW1wdHkscXVlcnlfaWQsIHBnX3N0YXRfYWN0aXZpdHk=?=
2025-09-04 03:32 UTC zhouenbing <zhouenbing@sunwoda-evb.com>
BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-06-18 19:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-06-18 21:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-06-21 20:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-06-21 20:42 UTC Dmitry Kovalenko <d.kovalenko@postgrespro.ru>
` Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-06-21 21:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-09-03 12:28 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-09-03 14:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-09-03 17:06 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c)
2025-09-03 20:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
[9+ messages in thread]
回复:Re: BUG #19040: Memory leak in hashed subplan node due to missing hashtempcxt reset
2025-09-03 16:59 UTC =?UTF-8?B?5p2O5rW35rSLKOmZjOeXlSk=?= <mohen.lhy@alibaba-inc.com>
BUG #18459: running pg_ctl.exe from inside a program running as a Windows service returns "error code 6"
2024-05-09 18:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18459: running pg_ctl.exe from inside a program running as a Windows service returns "error code 6"
2025-09-02 15:57 UTC Martin Fernau <martin.fernau@fernausoft.de>
[2+ messages in thread]
BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-07 12:19 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-08 07:03 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-08 07:57 UTC Georgy Shelkovy <g.shelkovy@arenadata.io>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-08 09:29 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-08 09:38 UTC Georgy Shelkovy <g.shelkovy@arenadata.io>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-08 09:47 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-08 10:12 UTC Georgy Shelkovy <g.shelkovy@arenadata.io>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-08 11:58 UTC Georgy Shelkovy <g.shelkovy@arenadata.io>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-08 13:07 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2024-08-09 15:26 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18575: Sometimes pg_rewind mistakenly assumes that nothing needs to be done.
2025-09-02 14:12 UTC Maxim Michkov <m.michkov@arenadata.io>
[11+ messages in thread]
BUG #19039: UNREACHABLE_CODE: Remove unreachable code in network_send - replace with assertion
2025-09-02 07:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19039: UNREACHABLE_CODE: Remove unreachable code in network_send - replace with assertion
2025-09-02 11:54 UTC Daniel Gustafsson <daniel@yesql.se>
[2+ messages in thread]
bug reapper: Empty query_id in pg_stat_activity
2025-08-28 09:22 UTC =?ISO-8859-1?B?ZHVvbWkucGVuZw==?= <duomi.peng@qq.com>
` Re: bug reapper: Empty query_id in pg_stat_activity
2025-08-28 11:07 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: bug reapper: Empty query_id in pg_stat_activity
2025-08-28 12:09 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: bug reapper: Empty query_id in pg_stat_activity
2025-08-28 12:25 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: bug reapper: Empty query_id in pg_stat_activity
2025-08-28 12:28 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: bug reapper: Empty query_id in pg_stat_activity
2025-08-28 12:42 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: bug reapper: Empty query_id in pg_stat_activity
2025-08-31 05:02 UTC Michael Paquier <michael@paquier.xyz>
` Re: bug reapper: Empty query_id in pg_stat_activity
2025-09-01 16:38 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: bug reapper: Empty query_id in pg_stat_activity
2025-09-02 04:59 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
[9+ messages in thread]
BUG #19031: pg_trgm infinite loop on certain cases
2025-08-25 21:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19031: pg_trgm infinite loop on certain cases
2025-08-26 00:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19031: pg_trgm infinite loop on certain cases
2025-08-26 11:26 UTC Arseniy Mukhin <arseniy.mukhin.dev@gmail.com>
` Re: BUG #19031: pg_trgm infinite loop on certain cases
2025-08-26 15:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19031: pg_trgm infinite loop on certain cases
2025-08-27 08:33 UTC Arseniy Mukhin <arseniy.mukhin.dev@gmail.com>
` Re: BUG #19031: pg_trgm infinite loop on certain cases
2025-08-27 14:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19031: pg_trgm infinite loop on certain cases
2025-08-27 19:17 UTC Arseniy Mukhin <arseniy.mukhin.dev@gmail.com>
` Re: BUG #19031: pg_trgm infinite loop on certain cases
2025-08-31 22:13 UTC Alexander Korotkov <aekorotkov@gmail.com>
[8+ messages in thread]
BUG #19036: Failed prepared INSERT statement make another SELECT query generate wrong result
2025-08-29 11:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19036: Failed prepared INSERT statement make another SELECT query generate wrong result
2025-08-29 15:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19036: Failed prepared INSERT statement make another SELECT query generate wrong result
2025-08-30 01:51 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
` Re: BUG #19036: Failed prepared INSERT statement make another SELECT query generate wrong result
2025-08-30 01:57 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19036: Failed prepared INSERT statement make another SELECT query generate wrong result
2025-08-30 02:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19036: Failed prepared INSERT statement make another SELECT query generate wrong result
2025-08-30 02:09 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
[6+ 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