pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedUse-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-07-31 06:43 UTC Michael Paquier <michael@paquier.xyz>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-07-31 16:51 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-07-31 22:09 UTC Michael Paquier <michael@paquier.xyz>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-08-01 04:33 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-08-01 04:52 UTC Michael Paquier <michael@paquier.xyz>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-08-01 10:00 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-08-01 11:45 UTC Michael Paquier <michael@paquier.xyz>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-08-01 16:32 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-08-02 03:27 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
2025-08-02 10:26 UTC Michael Paquier <michael@paquier.xyz>
[10+ messages in thread]
BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-06-20 12:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-06-20 19:53 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-06-20 20:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-06-20 21:20 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-06-20 22:48 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-06-25 16:06 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-07-22 02:27 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-07-24 16:30 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-07-24 21:06 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-07-25 14:15 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-07-28 21:15 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-07-28 21:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-07-30 19:13 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
2025-08-01 22:01 UTC Nathan Bossart <nathandbossart@gmail.com>
[14+ messages in thread]
BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-07-27 05:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-07-28 02:23 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-07-28 06:38 UTC Stepan Neretin <slpmcf@gmail.com>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-07-28 08:20 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-07-31 05:30 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-07-31 15:43 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-07-31 18:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-08-01 02:38 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-08-01 03:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-08-01 04:38 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-08-01 04:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops
2025-08-01 19:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
[12+ messages in thread]
BUG #19003: A SELECT that does not return a valid table
2025-07-30 19:20 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19003: A SELECT that does not return a valid table
2025-07-30 21:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19003: A SELECT that does not return a valid table
2025-07-30 21:38 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19003: A SELECT that does not return a valid table
2025-07-31 09:17 UTC Vik Fearing <vik@postgresfriends.org>
` Re: BUG #19003: A SELECT that does not return a valid table
2025-07-31 10:50 UTC Alexandre Bailly <alexandrebailly1955@gmail.com>
` Re: BUG #19003: A SELECT that does not return a valid table
2025-07-31 13:10 UTC Vik Fearing <vik@postgresfriends.org>
[6+ messages in thread]
BUG #19004: Incorrect lowercasing of word-final Greek capital Sigma (Σ)
2025-07-31 03:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19004: Incorrect lowercasing of word-final Greek capital Sigma (Σ)
2025-07-31 07:39 UTC John Naylor <johncnaylorls@gmail.com>
[2+ messages in thread]
BUG #15988: Improve ANALYZE-statement
2019-08-31 19:06 UTC PG Bug reporting form <noreply@postgresql.org>
` [PATCH v1 1/1] Allow ALTER SYSTEM to set unrecognized custom GUCs.
2025-07-30 18:34 UTC Nathan Bossart <nathan@postgresql.org>
` [PATCH v1 1/1] Allow ALTER SYSTEM to set unrecognized custom GUCs.
2025-07-30 18:34 UTC Nathan Bossart <nathan@postgresql.org>
[3+ messages in thread]
BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username`
2025-07-29 19:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username`
2025-07-29 19:54 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username`
2025-07-30 03:01 UTC Samuel Marks <samuelmarks@gmail.com>
` Re: BUG #19002: `pg_isready` unexpectedly succeeds on incorrect `--dbname` and/or `--username`
2025-07-30 03:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #19001: PostgreSQL 17: CREATE MATERIALIZED VIEW fails with STABLE function using JSONB LATERAL joins
2025-07-29 13:55 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19001: PostgreSQL 17: CREATE MATERIALIZED VIEW fails with STABLE function using JSONB LATERAL joins
2025-07-29 15:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19001: PostgreSQL 17: CREATE MATERIALIZED VIEW fails with STABLE function using JSONB LATERAL joins
2025-07-29 15:34 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[3+ messages in thread]
BUG #18987: psqlodbc_setup.exe installs as Unknown Publisher
2025-07-16 17:45 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18987: psqlodbc_setup.exe installs as Unknown Publisher
2025-07-28 11:51 UTC Daniel Gustafsson <daniel@yesql.se>
[2+ messages in thread]
Lower priority of the configure option --with-libraries causes wrong lib resolution
2025-06-15 16:20 UTC Charles Samborski <demurgos@demurgos.net>
` Re: Lower priority of the configure option --with-libraries causes wrong lib resolution
2025-06-15 20:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Lower priority of the configure option --with-libraries causes wrong lib resolution
2025-06-15 21:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Lower priority of the configure option --with-libraries causes wrong lib resolution
2025-07-27 22:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #18999: Equivalent queries processing WHERE IS NULL & WHERE IS NOT NULL produce mutually exclusive results
2025-07-25 04:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18999: Equivalent queries processing WHERE IS NULL & WHERE IS NOT NULL produce mutually exclusive results
2025-07-25 13:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18999: Equivalent queries processing WHERE IS NULL & WHERE IS NOT NULL produce mutually exclusive results
2025-07-25 14:40 UTC =?utf-8?B?SmluaHVpIExhaQ==?= <jinhui-lai@foxmail.com>
` Re: BUG #18999: Equivalent queries processing WHERE IS NULL & WHERE IS NOT NULL produce mutually exclusive results
2025-07-25 15:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18999: Equivalent queries processing WHERE IS NULL & WHERE IS NOT NULL produce mutually exclusive results
2025-07-25 16:22 UTC David G. Johnston <david.g.johnston@gmail.com>
[5+ messages in thread]
BUG #18996: Assertion fails in waiteventset.c when dropping database in single mode in PG18
2025-07-24 09:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18996: Assertion fails in waiteventset.c when dropping database in single mode in PG18
2025-07-24 13:46 UTC Patrick Stählin <me@packi.ch>
` Re: BUG #18996: Assertion fails in waiteventset.c when dropping database in single mode in PG18
2025-07-25 01:01 UTC Michael Paquier <michael@paquier.xyz>
[3+ messages in thread]
BUG #18998: No materialized views in INFORMATION_SCHEMA.TABLE_PRIVILEGES
2025-07-24 17:50 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18998: No materialized views in INFORMATION_SCHEMA.TABLE_PRIVILEGES
2025-07-24 21:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18997: Two equivalent queries return different results
2025-07-24 14:45 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18997: Two equivalent queries return different results
2025-07-24 17:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18997: Two equivalent queries return different results
2025-07-24 17:49 UTC =?utf-8?B?SmluaHVpIExhaQ==?= <jinhui-lai@foxmail.com>
[3+ messages in thread]
BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-04-16 23:14 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-04-16 23:54 UTC Zane Duffield <duffieldzane@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-04-21 06:09 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-04-21 06:40 UTC Shlok Kyal <shlok.kyal.oss@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-04-23 01:57 UTC Euler Taveira <euler@eulerto.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-04-23 03:13 UTC Zane Duffield <duffieldzane@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-04-23 03:30 UTC Zane Duffield <duffieldzane@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-04-24 03:38 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-04-24 06:25 UTC Shlok Kyal <shlok.kyal.oss@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-04-24 06:27 UTC Shlok Kyal <shlok.kyal.oss@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-04-25 08:44 UTC Shlok Kyal <shlok.kyal.oss@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-04-28 04:57 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-04-29 00:09 UTC Zane Duffield <duffieldzane@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-04-29 07:47 UTC Shlok Kyal <shlok.kyal.oss@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-05-05 14:47 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-05-10 19:19 UTC Shlok Kyal <shlok.kyal.oss@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-05-14 05:30 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-07-01 19:41 UTC Shlok Kyal <shlok.kyal.oss@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-07-10 07:03 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-07-22 11:24 UTC Shlok Kyal <shlok.kyal.oss@gmail.com>
` RE: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-07-22 12:21 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-07-23 04:35 UTC Shlok Kyal <shlok.kyal.oss@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-07-23 09:19 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-07-23 09:24 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-07-23 13:25 UTC Shlok Kyal <shlok.kyal.oss@gmail.com>
` Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load
2025-07-24 10:49 UTC Amit Kapila <amit.kapila16@gmail.com>
[26+ messages in thread]
BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message
2025-07-23 10:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message
2025-07-23 14:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message
2025-07-23 14:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message
2025-07-23 15:31 UTC Andrew Watkins <awatkins1966@gmail.com>
` Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message
2025-07-23 15:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message
2025-07-23 18:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message
2025-07-23 19:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18995: Building with GCC 14 fails: incompatible pointer struct pam_message
2025-07-24 10:28 UTC Andrew Watkins <awatkins1966@gmail.com>
[8+ messages in thread]
Self referential foreign keys in partitioned table not working as expected
2025-04-01 09:06 UTC Luca Vallisa <luca.vallisa@gmail.com>
` Re: Self referential foreign keys in partitioned table not working as expected
2025-04-01 10:18 UTC Christoph Berg <myon@debian.org>
` Re: Self referential foreign keys in partitioned table not working as expected
2025-04-01 10:24 UTC Luca Vallisa <luca.vallisa@gmail.com>
` Re: Self referential foreign keys in partitioned table not working as expected
2025-04-01 10:46 UTC Christoph Berg <myon@debian.org>
` Re: Self referential foreign keys in partitioned table not working as expected
2025-07-23 09:27 UTC Álvaro Herrera <alvherre@kurilemu.de>
[5+ messages in thread]
BUG #18992: Autovacuum triggering assert - LWLockAnyHeldByMe
2025-07-20 14:31 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18992: Autovacuum triggering assert - LWLockAnyHeldByMe
2025-07-21 05:52 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #18992: Autovacuum triggering assert - LWLockAnyHeldByMe
2025-07-21 07:21 UTC Rahila Syed <rahilasyed90@gmail.com>
` Re: BUG #18992: Autovacuum triggering assert - LWLockAnyHeldByMe
2025-07-23 01:39 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18992: Autovacuum triggering assert - LWLockAnyHeldByMe
2025-07-23 03:50 UTC Dilip Kumar <dilipbalaut@gmail.com>
[5+ messages in thread]
[PERFORMANCE] regression: EXECUTE loop TRUNCATE slower in 17.5 vs 17.2
2025-07-22 23:23 UTC Guilherme Luis França <gulybyte@gmail.com>
` Re: [PERFORMANCE] regression: EXECUTE loop TRUNCATE slower in 17.5 vs 17.2
2025-07-23 00:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #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]
[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