pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #19106: Potential regression with CTE materialization planning in Postgres 18
2025-11-09 13:52 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18
2025-11-09 15:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18
2025-11-10 03:21 UTC Kamil Monicz <kamil@monicz.dev>
` Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18
2025-11-10 17:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18
2025-11-10 21:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18
2025-11-11 15:16 UTC Vik Fearing <vik@postgresfriends.org>
` Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18
2025-11-11 15:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18
2025-11-11 16:53 UTC Vik Fearing <vik@postgresfriends.org>
` Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18
2025-11-11 19:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18
2025-11-11 20:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18
2025-11-12 07:04 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18
2025-11-12 19:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18
2025-11-13 03:49 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18
2025-11-14 17:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19106: Potential regression with CTE materialization planning in Postgres 18
2025-11-18 17:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
[15+ messages in thread]
BUG #19117: postgresql15-contrib-15.15 for RHEL 9 has conflicting OpenSSL dependencies (3.0.0 and 3.4.0)
2025-11-18 12:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19117: postgresql15-contrib-15.15 for RHEL 9 has conflicting OpenSSL dependencies (3.0.0 and 3.4.0)
2025-11-18 16:21 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: BUG #19117: postgresql15-contrib-15.15 for RHEL 9 has conflicting OpenSSL dependencies (3.0.0 and 3.4.0)
2025-11-18 16:56 UTC Devrim Gündüz <devrim@gunduz.org>
[3+ messages in thread]
TLS verification to intermediate trust anchor with psql
2025-10-21 08:15 UTC Miroslav Pankov <miroslav.pankov@broadcom.com>
` Re: TLS verification to intermediate trust anchor with psql
2025-10-21 20:44 UTC Jacob Champion <jacob.champion@enterprisedb.com>
` Re: TLS verification to intermediate trust anchor with psql
2025-11-18 14:11 UTC Miroslav Pankov <miroslav.pankov@broadcom.com>
[3+ messages in thread]
BUG #19116: Lost concurrent updates using ctid - as per doc guidance
2025-11-17 14:31 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19115: the package got zero size
2025-11-17 12:56 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19111: Using EXPLAIN ANALYZE with MERGE causes failed assert
2025-11-13 10:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19111: Using EXPLAIN ANALYZE with MERGE causes failed assert
2025-11-13 15:32 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19111: Using EXPLAIN ANALYZE with MERGE causes failed assert
2025-11-16 13:20 UTC Dilip Kumar <dilipbalaut@gmail.com>
` Re: BUG #19111: Using EXPLAIN ANALYZE with MERGE causes failed assert
2025-11-16 22:41 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
[4+ messages in thread]
BUG #19112: Error comes up on login to the QueryTool after update to PgAdmin 9.10
2025-11-14 09:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19112: Error comes up on login to the QueryTool after update to PgAdmin 9.10
2025-11-14 09:05 UTC Thomas Konrad <t.konrad.002@gmail.com>
` Re: BUG #19112: Error comes up on login to the QueryTool after update to PgAdmin 9.10
2025-11-14 16:21 UTC Greg Sabino Mullane <htamfids@gmail.com>
[3+ messages in thread]
postgresql16-contrib-16.11-1PGDG.rhel9.x86_64 fails to install on Rocky9 due to OPENSSSL version mismatch (not available)
2025-11-14 04:08 UTC Brodie, Kent <brodie@mcw.edu>
` Re: postgresql16-contrib-16.11-1PGDG.rhel9.x86_64 fails to install on Rocky9 due to OPENSSSL version mismatch (not available)
2025-11-14 09:32 UTC Horimoto Yasuhiro <horimoto@clear-code.com>
[2+ messages in thread]
[PATCH v1 1/1] GRANTED BY
2025-11-13 15:29 UTC Nathan Bossart <nathan@postgresql.org>
RLS creates inaccurate limit and offset results
2025-11-11 16:29 UTC mike@mikebrancato.com
` Re: RLS creates inaccurate limit and offset results
2025-11-11 22:10 UTC Christophe Pettus <xof@thebuild.com>
` Re: RLS creates inaccurate limit and offset results
2025-11-11 22:46 UTC mike@mikebrancato.com
` Re: RLS creates inaccurate limit and offset results
2025-11-12 18:20 UTC Christophe Pettus <xof@thebuild.com>
` Re: RLS creates inaccurate limit and offset results
2025-11-12 18:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #19110: the order of elements in a json object in database is different then the order of elements
2025-11-11 14:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19110: the order of elements in a json object in database is different then the order of elements
2025-11-11 15:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Functions 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]
[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