agora inbox for pgsql-bugs@postgresql.org
help / color / mirror / Atom feedBUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-19 17:37 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-21 23:49 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-22 12:12 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-22 12:37 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-23 03:43 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-23 17:51 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-24 02:43 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-24 06:22 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-25 04:29 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-26 00:09 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows
2026-09-28 07:01 UTC shihao zhong <zhong950419@gmail.com>
[11+ messages in thread]
PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
2026-09-27 06:07 UTC Jacky Nguyen <nktpro@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
2026-09-27 10:33 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
2026-09-28 06:37 UTC shihao zhong <zhong950419@gmail.com>
[3+ messages in thread]
BUG #19723: CREATE INDEX racing with ALTER INDEX ATTACH PARTITION triggers unexpected internal error
2026-09-26 09:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19723: CREATE INDEX racing with ALTER INDEX ATTACH PARTITION triggers unexpected internal error
2026-09-26 14:25 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19723: CREATE INDEX racing with ALTER INDEX ATTACH PARTITION triggers unexpected internal error
2026-09-28 04:44 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
[3+ messages in thread]
BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption
2026-09-13 16:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption
2026-09-15 08:59 UTC Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption
2026-09-27 16:11 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption
2026-09-27 16:14 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption
2026-09-27 19:05 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption
2026-09-27 20:35 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19686: Rolling back SET TABLESPACE + INSERT leads to index corruption
2026-09-28 04:13 UTC Peter Geoghegan <pg@bowt.ie>
[7+ messages in thread]
BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
2026-08-15 03:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
2026-08-16 14:29 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
2026-08-18 02:06 UTC =?ISO-8859-1?B?emVuZ21hbg==?= <zengman@halodbtech.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
2026-08-18 08:56 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
2026-09-04 10:38 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
2026-09-23 20:12 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
2026-09-24 17:06 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
2026-09-24 17:38 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
2026-09-26 16:28 UTC jian he <jian.universality@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
2026-09-26 18:14 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
2026-09-28 04:03 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[11+ messages in thread]
BUG #19725: PostgreSQL 18.6: pg_restore read failure with io_uring, not observed with worker
2026-09-28 03:34 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19670: Silent Integer Overflow in time_pl_interval() Returns Wrong Time Value
2026-09-07 14:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19670: Silent Integer Overflow in time_pl_interval() Returns Wrong Time Value
2026-09-26 15:25 UTC Rahul Yadav <rahul@rhyadav.com>
` Re: BUG #19670: Silent Integer Overflow in time_pl_interval() Returns Wrong Time Value
2026-09-27 17:57 UTC Andrew Krylosov <krylosov.andrew@gmail.com>
[3+ messages in thread]
BUG #19701: GIN trigram index loses rows at similarity_threshold 0
2026-09-19 05:17 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19701: GIN trigram index loses rows at similarity_threshold 0
2026-09-23 19:26 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19701: GIN trigram index loses rows at similarity_threshold 0
2026-09-25 09:09 UTC Palak Chaturvedi <chaturvedipalak1911@gmail.com>
` Re: BUG #19701: GIN trigram index loses rows at similarity_threshold 0
2026-09-25 15:38 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19701: GIN trigram index loses rows at similarity_threshold 0
2026-09-27 15:08 UTC Palak Chaturvedi <chaturvedipalak1911@gmail.com>
[5+ messages in thread]
BUG #19688: pg_dump --schema scans all sequences in PostgreSQL 18, causing severe performance regression
2026-09-14 20:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19688: pg_dump --schema scans all sequences in PostgreSQL 18, causing severe performance regression
2026-09-26 19:01 UTC Andrew Krylosov <krylosov.andrew@gmail.com>
[2+ messages in thread]
BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ
2026-08-02 17:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ
2026-09-04 08:01 UTC Grigorev Jurij <ju.grigorev@ftdata.ru>
` Re: BUG #19599: RestoreBlockImage: the decode cross-checks never bound hole_offset + hole_length against BLCKSZ
2026-09-26 16:54 UTC Rahul Yadav <rahul@rhyadav.com>
[3+ messages in thread]
BUG #19718: pg_dump -Ft: restore.sql gets "\unrestrict (null)"/"\restrict (null)", so psql skips \i data files
2026-09-24 21:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19718: pg_dump -Ft: restore.sql gets "\unrestrict (null)"/"\restrict (null)", so psql skips \i data files
2026-09-26 16:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19722: Window PARTITION BY numeric treats equal values with different scales as separate partitions
2026-09-26 08:55 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19722: Window PARTITION BY numeric treats equal values with different scales as separate partitions
2026-09-26 14:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
2026-09-25 19:38 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
2026-09-26 09:02 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
2026-09-26 09:31 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19720: pg_trgm GiST index corruption from gtrgm_union() dropping SIGNKEY
2026-09-26 14:26 UTC Nate Clark <natec425@gmail.com>
[4+ messages in thread]
BUG #19724: ALTER TYPE ... ALTER ATTRIBUTE triggers internal error for base type of domain with check
2026-09-26 13:00 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19562: pgcli packaged by the PostgreSQL Yum Repository:ModuleNotFoundError: No module named 'pgspecial'
2026-07-21 06:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19562: pgcli packaged by the PostgreSQL Yum Repository:ModuleNotFoundError: No module named 'pgspecial'
2026-07-27 17:47 UTC Pritt Balagopal <pritt1999@gmail.com>
` Re: BUG #19562: pgcli packaged by the PostgreSQL Yum Repository:ModuleNotFoundError: No module named 'pgspecial'
2026-09-20 11:12 UTC Pritt Balagopal <pritt1999@gmail.com>
` Re: BUG #19562: pgcli packaged by the PostgreSQL Yum Repository:ModuleNotFoundError: No module named 'pgspecial'
2026-09-26 10:10 UTC Pritt Balagopal <pritt1999@gmail.com>
[4+ messages in thread]
BUG #19721: json_value with DEFAULT ON ERROR returns inconsistent results for NULL input in materialized CTE
2026-09-26 06:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19721: json_value with DEFAULT ON ERROR returns inconsistent results for NULL input in materialized CTE
2026-09-26 08:55 UTC Andrey Rachitskiy <pl0h0yp1@gmail.com>
[2+ messages in thread]
autovacuum: automatically propagate updated parameters
2026-07-24 08:33 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-24 12:31 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-08-24 19:42 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-24 22:06 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-24 22:16 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-08-24 22:26 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-25 11:16 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-27 00:07 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-27 08:37 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-27 11:57 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-08-27 21:15 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-27 22:02 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-08-27 22:43 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-27 22:52 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: autovacuum: automatically propagate updated parameters
2026-08-28 07:13 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-08-28 22:31 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-09-21 18:28 UTC Nikolay Samokhvalov <nik@postgres.ai>
` Re: autovacuum: automatically propagate updated parameters
2026-09-24 00:38 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-24 04:44 UTC Nikolay Samokhvalov <nik@postgres.ai>
` Re: autovacuum: automatically propagate updated parameters
2026-09-24 06:34 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-24 09:04 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-09-24 20:41 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-24 21:35 UTC Manu <manuelreyesbravo@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-24 23:46 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-25 00:50 UTC Manu <manuelreyesbravo@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-25 07:45 UTC Zsolt Parragi <zsolt.parragi@percona.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-25 08:41 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: autovacuum: automatically propagate updated parameters
2026-09-25 19:12 UTC Manu <manuelreyesbravo@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-25 21:41 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-25 22:03 UTC Manu <manuelreyesbravo@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-26 00:31 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: autovacuum: automatically propagate updated parameters
2026-09-26 04:37 UTC Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
[32+ messages in thread]
BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
2026-09-22 16:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
2026-09-23 19:02 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
2026-09-24 04:22 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
2026-09-24 05:56 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
2026-09-24 06:13 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
2026-09-24 06:16 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
2026-09-24 06:34 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
2026-09-24 06:44 UTC jian he <jian.universality@gmail.com>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
2026-09-24 22:52 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
2026-09-24 23:46 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
2026-09-25 01:04 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
2026-09-25 19:35 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
2026-09-25 19:45 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: BUG #19715: pg_restore_attribute_stats() rejects range statistics for a domain over int4multirange
2026-09-25 23:53 UTC Michael Paquier <michael@paquier.xyz>
[14+ messages in thread]
42P16 error when dropping and adding column
2026-09-17 09:51 UTC Ludvig Janiuk <ludvig.janiuk@proton.me>
` Re: 42P16 error when dropping and adding column
2026-09-17 14:22 UTC Fujii Masao <masao.fujii@gmail.com>
` Re: 42P16 error when dropping and adding column
2026-09-17 15:01 UTC Manuel Reyes Bravo <manuelreyesbravo@gmail.com>
` Re: 42P16 error when dropping and adding column
2026-09-24 14:09 UTC Ludvig Janiuk <ludvig.janiuk@proton.me>
` Re: 42P16 error when dropping and adding column
2026-09-25 00:50 UTC Manu <manuelreyesbravo@gmail.com>
` Re: 42P16 error when dropping and adding column
2026-09-25 14:06 UTC Ludvig Janiuk <ludvig.janiuk@proton.me>
[6+ messages in thread]
BUG #19699: LIKE with a trailing escape fails to raise SQLSTATE 22025 for empty input
2026-09-18 07:31 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19699: LIKE with a trailing escape fails to raise SQLSTATE 22025 for empty input
2026-09-25 04:59 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19699: LIKE with a trailing escape fails to raise SQLSTATE 22025 for empty input
2026-09-25 05:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19699: LIKE with a trailing escape fails to raise SQLSTATE 22025 for empty input
2026-09-25 13:35 UTC shihao zhong <zhong950419@gmail.com>
[4+ messages in thread]
BUG #19719: BUG: huge_pages=on shared memory reattached without FILE_MAP_LARGE_PAGES on Windows
2026-09-25 04:39 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19714: pgcrypto pgp_sym_encrypt accepts nonnumeric s2k-mode as mode 0
2026-09-22 16:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19714: pgcrypto pgp_sym_encrypt accepts nonnumeric s2k-mode as mode 0
2026-09-25 04:37 UTC shihao zhong <zhong950419@gmail.com>
[2+ messages in thread]
BUG #19695: JSON_VALUE ... RETURNING jsonb returns NULL for later evaluation once one evaluation returns NULL
2026-09-18 02:45 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19695: JSON_VALUE ... RETURNING jsonb returns NULL for later evaluation once one evaluation returns NULL
2026-09-18 15:03 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19695: JSON_VALUE ... RETURNING jsonb returns NULL for later evaluation once one evaluation returns NULL
2026-09-19 00:58 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19695: JSON_VALUE ... RETURNING jsonb returns NULL for later evaluation once one evaluation returns NULL
2026-09-23 20:12 UTC Manu <manuelreyesbravo@gmail.com>
` Re: BUG #19695: JSON_VALUE ... RETURNING jsonb returns NULL for later evaluation once one evaluation returns NULL
2026-09-24 17:03 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19695: JSON_VALUE ... RETURNING jsonb returns NULL for later evaluation once one evaluation returns NULL
2026-09-24 20:49 UTC Manu <manuelreyesbravo@gmail.com>
[6+ messages in thread]
BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
2026-09-14 05:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
2026-09-14 19:07 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
2026-09-15 06:57 UTC Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
2026-09-23 18:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
2026-09-23 18:59 UTC Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
2026-09-23 19:39 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
` Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
2026-09-24 01:19 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #19687: ALTER SEQUENCE provokes error XX001 could not read blocks
2026-09-24 02:47 UTC Ayush Tiwari <ayushtiwari.slg01@gmail.com>
[8+ messages in thread]
BUG #19708: Hash Join becomes about 300x slower with higher work_mem
2026-09-20 11:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19708: Hash Join becomes about 300x slower with higher work_mem
2026-09-20 20:05 UTC Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19708: Hash Join becomes about 300x slower with higher work_mem
2026-09-20 20:52 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19708: Hash Join becomes about 300x slower with higher work_mem
2026-09-20 21:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19708: Hash Join becomes about 300x slower with higher work_mem
2026-09-21 23:31 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #19708: Hash Join becomes about 300x slower with higher work_mem
2026-09-22 04:34 UTC Alexandre Felipe <o.alexandre.felipe@gmail.com>
` Re: BUG #19708: Hash Join becomes about 300x slower with higher work_mem
2026-09-24 01:02 UTC shihao zhong <zhong950419@gmail.com>
[7+ messages in thread]
[next (older)]
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox