pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18993: [BUG] Unreachable code in pg_next_dst_boundary()
2025-07-21 12:29 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18993: [BUG] Unreachable code in pg_next_dst_boundary()
2025-07-21 14:29 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18993: [BUG] Unreachable code in pg_next_dst_boundary()
2025-07-21 14:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
2025-07-15 16:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
2025-07-15 18:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
2025-07-16 00:10 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
2025-07-16 09:33 UTC Yaroslav Syrytsia <me@ys.lc>
` Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
2025-07-16 09:55 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
2025-07-16 10:42 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
2025-07-16 10:48 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
2025-07-16 13:05 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
2025-07-17 05:44 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
2025-07-17 06:46 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
2025-07-18 09:19 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #18986: SIGSEGV in nodeModifyTable.c during Parallel Execution
2025-07-18 10:36 UTC Yaroslav Syrytsia <me@ys.lc>
[12+ messages in thread]
BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-14 19:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-14 19:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-14 19:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-14 21:11 UTC Aleksander Alekseev <aleksander@tigerdata.com>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-14 21:33 UTC Aleksander Alekseev <aleksander@tigerdata.com>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-14 21:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-14 22:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-14 23:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-15 03:54 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-15 04:52 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-15 04:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-15 12:33 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-15 14:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-15 16:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-15 23:32 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-15 23:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-16 04:45 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-17 12:03 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-17 13:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-17 15:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
2025-07-17 15:48 UTC Álvaro Herrera <alvherre@kurilemu.de>
[21+ messages in thread]
BUG #18989: Output of \sf does not match original source for E quoted strings (unlike \df+ used to)
2025-07-17 10:15 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18989: Output of \sf does not match original source for E quoted strings (unlike \df+ used to)
2025-07-17 13:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Correct Behaviour for Concurrent partition detach
2025-07-17 09:25 UTC Rohit Negi <rohit25.negi@gmail.com>
` Re: Correct Behaviour for Concurrent partition detach
2025-07-17 13:20 UTC Álvaro Herrera <alvherre@kurilemu.de>
[2+ messages in thread]
BUG #18990: The results of equivalent queries are inconsistent (one returns 0, another returns -0)
2025-07-17 11:30 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18990: The results of equivalent queries are inconsistent (one returns 0, another returns -0)
2025-07-17 12:06 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18990: The results of equivalent queries are inconsistent (one returns 0, another returns -0)
2025-07-17 13:09 UTC Dilip Kumar <dilipbalaut@gmail.com>
[3+ messages in thread]
PostgreSQL 18 beta1 - Segmentation fault on custom type casting
2025-07-10 04:35 UTC Thomas Thai <thomas.t.thai@gmail.com>
` Re: PostgreSQL 18 beta1 - Segmentation fault on custom type casting
2025-07-10 10:59 UTC Aleksander Alekseev <aleksander@tigerdata.com>
` Re: PostgreSQL 18 beta1 - Segmentation fault on custom type casting
2025-07-10 14:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL 18 beta1 - Segmentation fault on custom type casting
2025-07-16 22:54 UTC Thomas Thai <thomas.t.thai@gmail.com>
[4+ messages in thread]
info
2019-08-31 12:14 UTC Panagiotis Zachariadis <zachapan80@gmail.com>
` Re: info
2019-08-31 14:47 UTC David G. Johnston <david.g.johnston@gmail.com>
` [PATCH] Remove assertion in PortalRunMulti, simplify comment
2025-07-15 12:22 UTC Álvaro Herrera <alvherre@kurilemu.de>
[3+ messages in thread]
BUG #18983: Problems with Postgres "make check" under ASAN
2025-07-09 17:19 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18983: Problems with Postgres "make check" under ASAN
2025-07-09 18:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18983: Problems with Postgres "make check" under ASAN
2025-07-14 12:33 UTC Dmitry Kovalenko <d.kovalenko@postgrespro.ru>
` Re: BUG #18983: Problems with Postgres "make check" under ASAN
2025-07-14 13:41 UTC Aleksander Alekseev <aleksander@tigerdata.com>
[4+ messages in thread]
The same 2PC data maybe recovered twice
2023-07-06 02:02 UTC =?UTF-8?B?6JSh5qKm5aifKOeOiuS6jik=?= <mengjuan.cmj@alibaba-inc.com>
` 回复：The same 2PC data maybe recovered twice
2023-07-07 09:48 UTC =?UTF-8?B?6JSh5qKm5aifKOeOiuS6jik=?= <mengjuan.cmj@alibaba-inc.com>
` Re: The same 2PC data maybe recovered twice
2023-07-12 02:57 UTC Andy Fan <zhihui.fan1213@gmail.com>
` Re: The same 2PC data maybe recovered twice
2023-07-12 07:20 UTC suyu.cmj <mengjuan.cmj@alibaba-inc.com>
` Re: The same 2PC data maybe recovered twice
2023-07-13 06:58 UTC Michael Paquier <michael@paquier.xyz>
` Re: The same 2PC data maybe recovered twice
2023-07-17 06:26 UTC suyu.cmj <mengjuan.cmj@alibaba-inc.com>
` Re: The same 2PC data maybe recovered twice
2023-07-17 07:59 UTC Michael Paquier <michael@paquier.xyz>
` Re: The same 2PC data maybe recovered twice
2023-07-17 09:20 UTC suyu.cmj <mengjuan.cmj@alibaba-inc.com>
` Re: The same 2PC data maybe recovered twice
2023-07-18 05:13 UTC Michael Paquier <michael@paquier.xyz>
` Re: The same 2PC data maybe recovered twice
2025-07-09 01:57 UTC suyu.cmj <mengjuan.cmj@alibaba-inc.com>
` Re: The same 2PC data maybe recovered twice
2025-07-09 05:51 UTC suyu.cmj <mengjuan.cmj@alibaba-inc.com>
` Re: The same 2PC data maybe recovered twice
2025-07-09 07:35 UTC Michael Paquier <michael@paquier.xyz>
` Re: The same 2PC data maybe recovered twice
2025-07-14 06:46 UTC =?UTF-8?B?Q0FJLCBNZW5nanVhbg==?= <mengjuan.cmj@alibaba-inc.com>
` Re: The same 2PC data maybe recovered twice
2025-07-14 08:14 UTC Michael Paquier <michael@paquier.xyz>
` Re: The same 2PC data maybe recovered twice
2025-07-14 09:57 UTC suyu.cmj <mengjuan.cmj@alibaba-inc.com>
[15+ messages in thread]
Starting a PostgreSQL server on a dynamic port (parameter port=0)
2025-07-10 07:15 UTC a.mitrokhin@postgrespro.ru
` Re: Starting a PostgreSQL server on a dynamic port (parameter port=0)
2025-07-10 07:46 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Starting a PostgreSQL server on a dynamic port (parameter port=0)
2025-07-10 08:29 UTC a.mitrokhin@postgrespro.ru
` Re: Starting a PostgreSQL server on a dynamic port (parameter port=0)
2025-07-10 08:53 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Starting a PostgreSQL server on a dynamic port (parameter port=0)
2025-07-10 09:13 UTC Jim Jones <jim.jones@uni-muenster.de>
` Re: Starting a PostgreSQL server on a dynamic port (parameter port=0)
2025-07-10 13:21 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Starting a PostgreSQL server on a dynamic port (parameter port=0)
2025-07-10 14:12 UTC Euler Taveira <euler@eulerto.com>
` Re: Starting a PostgreSQL server on a dynamic port (parameter port=0)
2025-07-10 14:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Starting a PostgreSQL server on a dynamic port (parameter port=0)
2025-07-11 07:11 UTC a.mitrokhin@postgrespro.ru
[9+ messages in thread]
Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-04 09:54 UTC Gunnar Morling <gunnar.morling@googlemail.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-04 12:14 UTC Nisha Moond <nisha.moond412@gmail.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-04 14:12 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-04 15:22 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-04 16:07 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-04 16:24 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-04 18:59 UTC Gunnar Morling <gunnar.morling@googlemail.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-04 22:08 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-05 04:06 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-05 04:22 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-05 05:35 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-05 05:55 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-05 06:16 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-05 08:47 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-05 14:38 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-05 14:44 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-05 15:07 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-05 15:10 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-05 15:12 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-05 15:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-05 16:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-08 16:42 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-08 16:53 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-09 06:00 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-09 06:35 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-09 07:12 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` RE: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-09 07:24 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-09 09:21 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-09 10:19 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-09 15:17 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-10 03:27 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-10 05:27 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-10 05:51 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-10 10:27 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-10 11:58 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-10 23:48 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-11 02:32 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Unexpected behavior when setting "idle_replication_slot_timeout"
2025-07-11 06:57 UTC Gunnar Morling <gunnar.morling@googlemail.com>
[38+ messages in thread]
BUG #18961: Race scenario where max_standby_streaming_delay is not honored
2025-06-19 00:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored
2025-06-19 15:17 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored
2025-06-19 15:58 UTC Anthony Hsu <erwaman@gmail.com>
` Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored
2025-06-27 05:05 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored
2025-06-27 06:11 UTC Anthony Hsu <erwaman@gmail.com>
` Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored
2025-06-27 06:26 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored
2025-06-28 23:37 UTC Anthony Hsu <erwaman@gmail.com>
` Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored
2025-06-30 03:28 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored
2025-07-10 22:36 UTC Anthony Hsu <erwaman@gmail.com>
[9+ messages in thread]
BUG #18965: Issue with Short-Circuit Evaluation in Boolean Expressions
2025-06-20 17:42 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18965: Issue with Short-Circuit Evaluation in Boolean Expressions
2025-06-20 18:14 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18965: Issue with Short-Circuit Evaluation in Boolean Expressions
2025-06-20 18:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18965: Issue with Short-Circuit Evaluation in Boolean Expressions
2025-07-08 17:34 UTC Jeff Davis <pgsql@j-davis.com>
` Re: BUG #18965: Issue with Short-Circuit Evaluation in Boolean Expressions
2025-07-08 17:48 UTC Jeff Davis <pgsql@j-davis.com>
[5+ messages in thread]
BUG #18981: Fault tolerance and improvement for xmltotext_with_options (xml.c)
2025-07-08 09:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18981: Fault tolerance and improvement for xmltotext_with_options (xml.c)
2025-07-08 16:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18980: Unable to perform make due to inability to resolve a variety of Undefined symbols arm64
2025-07-07 21:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18980: Unable to perform make due to inability to resolve a variety of Undefined symbols arm64
2025-07-07 21:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18801: JIT recompiles function for each row if custom aggregation function is used
2025-02-09 17:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18801: JIT recompiles function for each row if custom aggregation function is used
2025-02-10 08:25 UTC Vladlen Popolitov <v.popolitov@postgrespro.ru>
` Re: BUG #18801: JIT recompiles function for each row if custom aggregation function is used
2025-07-07 10:02 UTC Yura Sokolov <y.sokolov@postgrespro.ru>
[3+ messages in thread]
BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1
2025-07-06 13:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1
2025-07-06 15:11 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1
2025-07-06 15:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1
2025-07-06 16:41 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1
2025-07-06 16:47 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18979: pg_upgrade to PG17 fails if max_slot_wal_keep_size is not set to -1
2025-07-06 17:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
[6+ messages in thread]
functional index search path issue.
2025-07-05 11:45 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: functional index search path issue.
2025-07-05 14:53 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-06-28 07:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-06-29 05:28 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-06-29 17:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-06-29 17:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-06-30 01:47 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-06-30 02:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-06-30 06:04 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-06-30 15:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-07-01 03:25 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-07-01 19:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure
2025-07-03 17:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
[11+ messages in thread]
BUG #18978: Index does not work in aggregate function filter
2025-07-03 16:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18978: Index does not work in aggregate function filter
2025-07-03 16:36 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18977: Unexpected result of function to_char
2025-07-03 13:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18977: Unexpected result of function to_char
2025-07-03 14:40 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18977: Unexpected result of function to_char
2025-07-03 15:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18977: Unexpected result of function to_char
2025-07-03 15:49 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
[4+ messages in thread]
BUG #16931: source code problem about commit_ts
2021-03-18 04:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16931: source code problem about commit_ts
2021-03-18 10:19 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #16931: source code problem about commit_ts
2021-03-24 09:05 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #16931: source code problem about commit_ts
2021-03-24 10:25 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #16931: source code problem about commit_ts
2021-03-24 16:39 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #16931: source code problem about commit_ts
2021-03-25 02:59 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #16931: source code problem about commit_ts
2021-04-09 22:42 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #16931: source code problem about commit_ts
2021-04-11 15:09 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #16931: source code problem about commit_ts
2025-07-02 01:42 UTC Andy Fan <zhihuifan1213@163.com>
` Re: BUG #16931: source code problem about commit_ts
2025-07-02 08:44 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #16931: source code problem about commit_ts
2025-07-03 13:33 UTC Andy Fan <zhihuifan1213@163.com>
` Re: BUG #16931: source code problem about commit_ts
2025-07-03 14:42 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
[12+ messages in thread]
BUG #18976: -0.0 with float8 will be transformed to 0 in prepare statement but not in normal execution
2025-07-03 03:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18976: -0.0 with float8 will be transformed to 0 in prepare statement but not in normal execution
2025-07-03 12:23 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18976: -0.0 with float8 will be transformed to 0 inprepare statement but not in normal execution
2025-07-03 12:30 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
` Re: BUG #18976: -0.0 with float8 will be transformed to 0 inprepare statement but not in normal execution
2025-07-03 13:27 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18976: -0.0 with float8 will be transformed to 0 inpreparestatement but not in normal execution
2025-07-03 13:45 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
[5+ messages in thread]
BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries
2025-07-01 22:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries
2025-07-02 00:03 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries
2025-07-02 06:35 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries
2025-07-02 07:04 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries
2025-07-02 07:44 UTC Sergei Kornilov <sk@zsrv.org>
` Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries
2025-07-02 19:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
[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