pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedFunctions used by index don't need to be immutable?
2025-11-11 12:35 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Functions used by index don't need to be immutable?
2025-11-11 12:43 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: Functions used by index don't need to be immutable?
2025-11-11 12:43 UTC hubert depesz lubaczewski <depesz@depesz.com>
[3+ messages in thread]
BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-24 14:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-25 14:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-27 10:21 UTC Lori Corbani <Lori.Corbani@jax.org>
` RE: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-27 11:34 UTC Lori Corbani <Lori.Corbani@jax.org>
` RE: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-27 16:32 UTC Lori Corbani <Lori.Corbani@jax.org>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-27 19:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-27 20:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-28 00:58 UTC Richard Guo <guofenglinux@gmail.com>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-28 01:04 UTC Richard Guo <guofenglinux@gmail.com>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-28 02:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-28 08:46 UTC Richard Guo <guofenglinux@gmail.com>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-28 23:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-29 01:46 UTC Richard Guo <guofenglinux@gmail.com>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-29 06:45 UTC Richard Guo <guofenglinux@gmail.com>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-29 16:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-30 03:24 UTC Richard Guo <guofenglinux@gmail.com>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-30 03:43 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-30 04:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-30 09:57 UTC Lori Corbani <Lori.Corbani@jax.org>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-30 10:11 UTC John Naylor <johncnaylorls@gmail.com>
` RE: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-30 10:13 UTC Lori Corbani <Lori.Corbani@jax.org>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-30 10:35 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-30 10:40 UTC David Rowley <dgrowleyml@gmail.com>
` RE: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-10-30 10:43 UTC Lori Corbani <Lori.Corbani@jax.org>
` Re: [EXTERNAL]Re: BUG #19094: select statement on postgres 17 vs postgres 18 is returning different/duplicate results
2025-11-11 03:39 UTC Thomas Munro <thomas.munro@gmail.com>
[25+ messages in thread]
BUG #19108: Stack overflow duting query parse
2025-11-10 11:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19108: Stack overflow duting query parse
2025-11-10 12:38 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #19108: Stack overflow duting query parse
2025-11-10 13:23 UTC Andrey Zhidenkov <pensnarik@gmail.com>
` Re: BUG #19108: Stack overflow duting query parse
2025-11-10 16:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19108: Stack overflow duting query parse
2025-11-10 16:12 UTC Andrey Zhidenkov <pensnarik@gmail.com>
` Re: BUG #19108: Stack overflow duting query parse
2025-11-10 17:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
[6+ messages in thread]
BUG #19107: The hold cursor is unexpectedly released during rollback
2025-11-10 10:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re:BUG #19107: The hold cursor is unexpectedly released during rollback
2025-11-10 10:50 UTC =?gb18030?B?emVuZ21hbg==?= <zengman@halodbtech.com>
` Re: BUG #19107: The hold cursor is unexpectedly released during rollback
2025-11-10 16:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19107: The hold cursor is unexpectedly released during rollback
2025-11-10 16:37 UTC =?gb18030?B?emVuZ21hbg==?= <zengman@halodbtech.com>
[4+ messages in thread]
clog segment truncation
2025-11-10 12:29 UTC Smolkin Grigory <smallkeen@gmail.com>
` Re: clog segment truncation
2025-11-10 13:05 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: clog segment truncation
2025-11-10 13:43 UTC Matheus Alcantara <matheusssilv97@gmail.com>
` Re: clog segment truncation
2025-11-10 14:35 UTC Smolkin Grigory <smallkeen@gmail.com>
[4+ messages in thread]
ecpg Fetch issue
2025-11-09 13:26 UTC Tzuriel Kahlon <tzuriel.kahlon@surecomp.com>
` Re: ecpg Fetch issue
2025-11-10 11:43 UTC Heikki Linnakangas <hlinnaka@iki.fi>
[2+ messages in thread]
BUG #19105: Parallel Hash Join crash when work_mem is small
2025-11-08 22:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19105: Parallel Hash Join crash when work_mem is small
2025-11-09 15:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19105: Parallel Hash Join crash when work_mem is small
2025-11-09 17:49 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #19105: Parallel Hash Join crash when work_mem is small
2025-11-09 22:35 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #19105: Parallel Hash Join crash when work_mem is small
2025-11-09 23:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-10-23 09:09 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-10-24 06:20 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-10-24 08:33 UTC xingguo <ryanzxg@gmail.com>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-10-24 08:47 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-10-24 15:11 UTC Euler Taveira <euler@eulerto.com>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-10-27 04:12 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-10-29 05:01 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-10-29 06:36 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-10-29 23:36 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-10-30 16:07 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-10-31 03:16 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-10-31 10:50 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-11-01 00:17 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-11-01 00:44 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-11-04 04:52 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-11-04 09:01 UTC Xuneng Zhou <xunengzhou@gmail.com>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-11-04 09:31 UTC xingguo <ryanzxg@gmail.com>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-11-04 09:48 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-11-05 01:46 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-11-08 20:03 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
2025-11-09 22:36 UTC Michael Paquier <michael@paquier.xyz>
[21+ messages in thread]
BUG #19103: Canceled INSERT statement can still influence the performance of subsequent SELECT statement
2025-11-04 12:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19103: Canceled INSERT statement can still influence the performance of subsequent SELECT statement
2025-11-04 13:26 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #19103: Canceled INSERT statement can still influence the performance of subsequent SELECT statement
2025-11-04 14:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19103: Canceled INSERT statement can still influence the performance of subsequent SELECT statement
2025-11-07 15:51 UTC Álvaro Herrera <alvherre@kurilemu.de>
[4+ messages in thread]
BUG #19100: Different column type between partitioned table and detached pending partition table make errors
2025-11-01 18:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19100: Different column type between partitioned table and detached pending partition table make errors
2025-11-02 18:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19100: Different column type between partitioned table and detached pending partition table make errors
2025-11-03 09:16 UTC Haiyang Li <mohen.lhy@alibaba-inc.com>
` Re: BUG #19100: Different column type between partitioned table and detached pending partition table make errors
2025-11-05 14:59 UTC Haiyang Li <mohen.lhy@alibaba-inc.com>
[4+ messages in thread]
BUG #19104: Does regexp_substr function support non-greedy matching?
2025-11-05 12:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19104: Does regexp_substr function support non-greedy matching?
2025-11-05 14:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
CREATE TABLE ... LIKE INCLUDING ALL does not create new sequences for serial columns
2025-11-03 17:10 UTC Kumaresan Balakrishnan <kumaresan.balakrishnan@intics.ai>
` RE: CREATE TABLE ... LIKE INCLUDING ALL does not create new sequences for serial columns
2025-11-03 19:47 UTC Sivadhas arumugam <sivadhas.arumugam@intics.ai>
` Re: CREATE TABLE ... LIKE INCLUDING ALL does not create new sequences for serial columns
2025-11-05 13:01 UTC Peter Eisentraut <peter@eisentraut.org>
[3+ messages in thread]
BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown
2025-11-03 05:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown
2025-11-03 05:57 UTC Kuntal Ghosh <kuntalghosh.2007@gmail.com>
` Re: BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown
2025-11-03 10:09 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown
2025-11-03 13:09 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown
2025-11-04 07:44 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown
2025-11-04 09:51 UTC Kuntal Ghosh <kuntalghosh.2007@gmail.com>
` Re: BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown
2025-11-04 13:43 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown
2025-11-04 23:41 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown
2025-11-05 01:36 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown
2025-11-05 01:50 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown
2025-11-05 06:04 UTC Kuntal Ghosh <kuntalghosh.2007@gmail.com>
` Re: BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown
2025-11-05 08:30 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown
2025-11-05 10:19 UTC Richard Guo <guofenglinux@gmail.com>
[13+ messages in thread]
ALTER TABLE ... ADD COLUMN ... DEFAULT with volatile function loses DML
2025-11-04 18:14 UTC Jeff Davis <pgsql@j-davis.com>
` Re: ALTER TABLE ... ADD COLUMN ... DEFAULT with volatile function loses DML
2025-11-04 18:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: ALTER TABLE ... ADD COLUMN ... DEFAULT with volatile function loses DML
2025-11-04 19:20 UTC Jeff Davis <pgsql@j-davis.com>
[3+ messages in thread]
BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-03 11:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-03 11:45 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-03 11:48 UTC Matthias Hörmann <matthias.hoermann@saltation.com>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-03 14:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-03 19:09 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-03 19:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-03 19:34 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-03 20:58 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-10 05:26 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-09-10 09:24 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-22 21:23 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-22 21:53 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-24 22:26 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-27 14:30 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-27 19:49 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-27 21:21 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-29 15:24 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-29 15:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-10-29 20:19 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
2025-11-03 20:57 UTC Peter Eisentraut <peter@eisentraut.org>
[20+ messages in thread]
BUG #19101: Ceil on BIGINT could lost precision in decil function
2025-11-02 15:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19101: Ceil on BIGINT could lost precision in decil function
2025-11-02 16:31 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19101: Ceil on BIGINT could lost precision in decil function
2025-11-02 16:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re:Re: BUG #19101: Ceil on BIGINT could lost precision in decil function
2025-11-03 02:48 UTC dqetool <dqetool@126.com>
[4+ messages in thread]
Inconsistencies around Composite Row nullness
2025-11-02 16:52 UTC Chris Hanks <christopher.m.hanks@gmail.com>
` Re: Inconsistencies around Composite Row nullness
2025-11-02 18:19 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Inconsistencies around Composite Row nullness
2025-11-02 18:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
=?gb18030?B?u9i4tKO6IFtidWcgcmVwb3J0XSBBYm91dCBjcmVh?= =?gb18030?B?dGUgdGFibGUgbGlrZSBmZWF0dXJlJ3MgYnVn?=
2025-10-31 09:45 UTC =?gb18030?B?ZGVuZ2thaQ==?= <784523565@qq.com>
[bug report] About create table like feature's bug
2025-10-31 07:14 UTC =?gb18030?B?ZGVuZ2thaQ==?= <784523565@qq.com>
` Re: [bug report] About create table like feature's bug
2025-10-31 08:50 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
BUG #19096: Hugepages configuration is probably not reserving the allocated number of pages
2025-10-28 09:37 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19096: Hugepages configuration is probably not reserving the allocated number of pages
2025-10-29 19:08 UTC Tomas Vondra <tomas@vondra.me>
[2+ messages in thread]
BUG #19097: System catalog modifications are allowed by alter
2025-10-29 04:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19097: System catalog modifications are allowed by alter
2025-10-29 11:31 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19097: System catalog modifications are allowed by alter
2025-10-29 11:32 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19097: System catalog modifications are allowed by alter
2025-10-29 12:09 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19097: System catalog modifications are allowed by alter
2025-10-29 14:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
ERROR: found xmin 4133102167 from before relfrozenxid 4151440783
2025-09-12 16:39 UTC Tushar Takate <tushar11.takate@gmail.com>
` Re: ERROR: found xmin 4133102167 from before relfrozenxid 4151440783
2025-09-12 21:10 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: ERROR: found xmin 4133102167 from before relfrozenxid 4151440783
2025-09-13 01:10 UTC Tushar Takate <tushar11.takate@gmail.com>
` Re: ERROR: found xmin 4133102167 from before relfrozenxid 4151440783
2025-09-13 01:24 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: ERROR: found xmin 4133102167 from before relfrozenxid 4151440783
2025-09-13 04:38 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: ERROR: found xmin 4133102167 from before relfrozenxid 4151440783
2025-10-28 21:34 UTC surya poondla <suryapoondla4@gmail.com>
[6+ messages in thread]
Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-16 09:46 UTC Dmitry Fomin <fomin.list@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-17 01:21 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-17 09:08 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-17 10:36 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-20 13:48 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-20 19:27 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-21 01:28 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-21 05:20 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-21 09:11 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-21 11:22 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-21 13:49 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-21 20:29 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-23 12:07 UTC Amit Langote <amitlangote09@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-25 22:03 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
2025-10-28 12:44 UTC Amit Langote <amitlangote09@gmail.com>
[15+ messages in thread]
psql --echo-queries does not echo all queries
2025-10-24 18:16 UTC Gavin Wahl <gavinwahl@gmail.com>
` Re: psql --echo-queries does not echo all queries
2025-10-25 14:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: psql --echo-queries does not echo all queries
2025-10-27 22:24 UTC Gavin Wahl <gavinwahl@gmail.com>
[3+ messages in thread]
BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech
2025-10-21 07:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech
2025-10-21 13:14 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech
2025-10-21 15:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech
2025-10-23 00:29 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19092: scram_free() will free on address which was not malloc()-ed in pg_scram_mech
2025-10-23 15:05 UTC Jacob Champion <jacob.champion@enterprisedb.com>
[5+ 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