pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #19355: Attempt to insert data unexpectedly during concurrent update
2025-12-15 01:40 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2025-12-15 06:25 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2025-12-22 14:51 UTC Bh W <wangbihua.cn@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2025-12-22 22:37 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2025-12-24 08:08 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2025-12-24 12:07 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2025-12-24 23:11 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2025-12-25 04:48 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2025-12-31 16:16 UTC Bernice Southey <bernice.southey@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2026-01-01 21:58 UTC Bernice Southey <bernice.southey@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2026-01-07 09:37 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2026-01-07 09:45 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2026-01-07 11:18 UTC Bernice Southey <bernice.southey@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2026-01-07 12:16 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2026-01-07 12:52 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2026-01-08 13:16 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2026-01-15 11:39 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2026-01-15 16:34 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #19355: Attempt to insert data unexpectedly during concurrent update
2026-01-16 06:23 UTC Amit Langote <amitlangote09@gmail.com>
[19+ messages in thread]
Re[2]: BUG #19379: Role pg_read_all_data don't allowed read large objects
2026-01-15 14:05 UTC Глеб Борков <long76.git@mail.ru>
uninitialized var in encnames.c
2026-01-15 08:00 UTC ma lz <ma100@hotmail.com>
` 回复: uninitialized var in encnames.c
2026-01-15 08:06 UTC ma lz <ma100@hotmail.com>
[2+ messages in thread]
BUG #19378: How do you know to start Postgresql with "systemctl start postgresql@18-main" ?
2026-01-14 19:28 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19366: heap-use-after-free in pgaio_io_reclaim() detected with RELCACHE_FORCE_RELEASE
2025-12-29 06:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19366: heap-use-after-free in pgaio_io_reclaim() detected with RELCACHE_FORCE_RELEASE
2026-01-14 16:45 UTC Andres Freund <andres@anarazel.de>
[2+ messages in thread]
Inconsistent handling of signed zero (-0) between INNER JOIN and INTERSECT ALL
2026-01-12 16:25 UTC =?utf-8?B?5byA5b+D5bCP5biC5rCR?= <2530254482@qq.com>
` Re: Inconsistent handling of signed zero (-0) between INNER JOIN and INTERSECT ALL
2026-01-12 19:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #19375: PathTarget expression costs are being double-counted in the planner
2026-01-12 12:16 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19365: postgres 18 pg_dump fails whan drop sequence concurrently
2025-12-27 23:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19365: postgres 18 pg_dump fails whan drop sequence concurrently
2025-12-29 17:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19365: postgres 18 pg_dump fails whan drop sequence concurrently
2026-01-09 16:19 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #19365: postgres 18 pg_dump fails whan drop sequence concurrently
2026-01-09 22:56 UTC Paveł Tyślacki <pavel.tyslacki@gmail.com>
[4+ messages in thread]
Bug Report: PostgreSQL 16 crashes on ALTER USER CURRENT_USER WITH PASSWORD
2026-01-06 13:58 UTC Andrii <andriikrivich@gmail.com>
` Re: Bug Report: PostgreSQL 16 crashes on ALTER USER CURRENT_USER WITH PASSWORD
2026-01-07 16:32 UTC Andres Freund <andres@anarazel.de>
` Re: Bug Report: PostgreSQL 16 crashes on ALTER USER CURRENT_USER WITH PASSWORD
2026-01-07 16:33 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: Bug Report: PostgreSQL 16 crashes on ALTER USER CURRENT_USER WITH PASSWORD
2026-01-07 21:08 UTC Andrii <andriikrivich@gmail.com>
` Re: Bug Report: PostgreSQL 16 crashes on ALTER USER CURRENT_USER WITH PASSWORD
2026-01-07 21:14 UTC Andres Freund <andres@anarazel.de>
` Re: Bug Report: PostgreSQL 16 crashes on ALTER USER CURRENT_USER WITH PASSWORD
2026-01-08 04:45 UTC Gilles Darold <gilles@darold.net>
` Re: Bug Report: PostgreSQL 16 crashes on ALTER USER CURRENT_USER WITH PASSWORD
2026-01-08 11:36 UTC Andrii <andriikrivich@gmail.com>
[7+ messages in thread]
BUG #19372: Scan operator maybe output unnecessary columns to the upper-layer operators
2026-01-07 08:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19372: Scan operator maybe output unnecessary columns to the upper-layer operators
2026-01-07 09:25 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19372: Scan operator maybe output unnecessary columns to the upper-layer operators
2026-01-08 03:02 UTC David Rowley <dgrowleyml@gmail.com>
[3+ messages in thread]
BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
2026-01-06 05:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
2026-01-06 09:26 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
2026-01-06 15:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
2026-01-06 16:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
2026-01-06 16:45 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
2026-01-06 17:42 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
2026-01-06 18:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
2026-01-06 19:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19370: PG18 returns incorrect array slice results when slice bounds depend on another array expression
2026-01-07 01:04 UTC Andres Freund <andres@anarazel.de>
[9+ messages in thread]
BUG #19371: programı yüklerken hata veriyor
2026-01-06 05:57 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
2025-12-12 10:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
2025-12-12 16:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
2025-12-13 10:01 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
2025-12-15 14:28 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
2025-12-16 11:30 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
2025-12-24 02:15 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
2025-12-24 02:40 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
2025-12-25 03:58 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19353: Error XX000 if referencing expanded array in grouping set: variable not found in subplan target list
2026-01-05 08:31 UTC Marian Muller Rebeyrol <marian.muller@serli.com>
[9+ messages in thread]
BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
2025-10-29 09:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
2025-10-29 11:31 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
2025-10-29 12:43 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
2025-10-29 13:52 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
2025-10-29 15:03 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
2025-10-29 15:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
2025-10-29 15:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
2025-10-29 18:51 UTC Paul A Jungwirth <pj@illuminatedcomputing.com>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
2025-10-30 10:30 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
2025-10-30 17:20 UTC Paul A Jungwirth <pj@illuminatedcomputing.com>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
2025-10-30 18:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
2025-10-31 08:51 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
2025-10-31 09:11 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
2025-10-31 11:22 UTC Matthias van de Meent <boekewurm+postgres@gmail.com>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
2025-12-31 22:47 UTC Paul A Jungwirth <pj@illuminatedcomputing.com>
` Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
2026-01-02 18:32 UTC Paul A Jungwirth <pj@illuminatedcomputing.com>
[16+ messages in thread]
BUG #19368: f54af9f does not create the correct macro for autotools build
2025-12-31 00:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19368: f54af9f does not create the correct macro for autotools build
2025-12-31 15:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19368: f54af9f does not create the correct macro for autotools build
2025-12-31 16:50 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #19368: f54af9f does not create the correct macro for autotools build
2025-12-31 16:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19368: f54af9f does not create the correct macro for autotools build
2025-12-31 19:20 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #19368: f54af9f does not create the correct macro for autotools build
2026-01-02 14:28 UTC Andres Freund <andres@anarazel.de>
[6+ messages in thread]
GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-11-17 08:02 UTC Haowu Ge <gehaowu@bitmoe.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-11-18 08:27 UTC Richard Guo <guofenglinux@gmail.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-11-19 10:07 UTC Richard Guo <guofenglinux@gmail.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-12-08 06:10 UTC Richard Guo <guofenglinux@gmail.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-12-09 06:38 UTC Richard Guo <guofenglinux@gmail.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-12-09 08:54 UTC Haowu Ge <gehaowu@bitmoe.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-12-10 02:01 UTC Richard Guo <guofenglinux@gmail.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-12-11 02:32 UTC Haowu Ge <gehaowu@bitmoe.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-12-12 09:28 UTC Richard Guo <guofenglinux@gmail.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-12-15 01:23 UTC Haowu Ge <gehaowu@bitmoe.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-12-18 08:56 UTC Richard Guo <guofenglinux@gmail.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-12-24 07:50 UTC Richard Guo <guofenglinux@gmail.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-12-24 10:05 UTC Haowu Ge <gehaowu@bitmoe.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-12-28 04:20 UTC Richard Guo <guofenglinux@gmail.com>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-12-28 16:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: GROUP BY ROLLUP queries on views trigger full table scans (index usage not optimized)
2025-12-30 03:47 UTC Richard Guo <guofenglinux@gmail.com>
[16+ messages in thread]
BUG #19367: typos in backend/utils/adt/timestamp.c
2025-12-29 09:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19367: typos in backend/utils/adt/timestamp.c
2025-12-29 10:25 UTC Rahila Syed <rahilasyed90@gmail.com>
` Re: BUG #19367: typos in backend/utils/adt/timestamp.c
2025-12-29 10:35 UTC Japin Li <japinli@hotmail.com>
` RE: BUG #19367: typos in backend/utils/adt/timestamp.c
2025-12-29 12:20 UTC =?UTF-8?b?0J3QuNC60L7Qu9Cw0Lkg0KTQsNC00LXQtdCy?= <fadeymail@rambler.ru>
` Re: BUG #19367: typos in backend/utils/adt/timestamp.c
2025-12-29 15:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19367: typos in backend/utils/adt/timestamp.c
2025-12-30 02:30 UTC Japin Li <japinli@hotmail.com>
[6+ messages in thread]
Lost update in an ordered batch, but only with index scan
2025-12-28 23:07 UTC Bernice Southey <bernice.southey@gmail.com>
` Re: Lost update in an ordered batch, but only with index scan
2025-12-29 08:12 UTC Richard Guo <guofenglinux@gmail.com>
[2+ messages in thread]
Standby server with cascade logical replication could not be properly stopped under load
2025-05-22 02:19 UTC Alexey Makhmutov <a.makhmutov@postgrespro.ru>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-22 09:48 UTC Ajin Cherian <itsajin@gmail.com>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-22 10:33 UTC shveta malik <shveta.malik@gmail.com>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-22 13:29 UTC Alexey Makhmutov <a.makhmutov@postgrespro.ru>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-22 15:31 UTC Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-22 18:22 UTC Alexey Makhmutov <a.makhmutov@postgrespro.ru>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-22 23:47 UTC Michael Paquier <michael@paquier.xyz>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-28 07:35 UTC Michael Paquier <michael@paquier.xyz>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-28 16:12 UTC Alexey Makhmutov <a.makhmutov@postgrespro.ru>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-29 07:01 UTC Michael Paquier <michael@paquier.xyz>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-29 10:28 UTC Ajin Cherian <itsajin@gmail.com>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-05-29 23:32 UTC Michael Paquier <michael@paquier.xyz>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-06-02 03:17 UTC Michael Paquier <michael@paquier.xyz>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-12-26 11:14 UTC G. Sl <skokoveshat@gmail.com>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-12-29 00:09 UTC Michael Paquier <michael@paquier.xyz>
` Re: Standby server with cascade logical replication could not be properly stopped under load
2025-12-29 05:22 UTC G. Sl <skokoveshat@gmail.com>
[16+ messages in thread]
BUG #19363: PostgreSQL shared memory exhaustion during query execution involving views and parallel workers
2025-12-26 15:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19363: PostgreSQL shared memory exhaustion during query execution involving views and parallel workers
2025-12-27 05:12 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #19363: PostgreSQL shared memory exhaustion during query execution involving views and parallel workers
2025-12-27 17:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #19363: PostgreSQL shared memory exhaustion during query execution involving views and parallel workers
2025-12-27 21:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #19356: Unexpected result of prepared UPDATE with force_generic_plan
2025-12-16 03:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19356: Unexpected result of prepared UPDATE with force_generic_plan
2025-12-26 06:59 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
` Re: BUG #19356: Unexpected result of prepared UPDATE with force_generic_plan
2025-12-26 07:20 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #19356: Unexpected result of prepared UPDATE with force_generic_plan
2025-12-26 07:59 UTC =?utf-8?B?WmhhbmdDaGk=?= <798604270@qq.com>
[4+ messages in thread]
Regression: partial index with IS NOT NULL predicate not used for min/max optimization on NOT NULL columns
2025-12-24 16:46 UTC Dmytro Astapov <dastapov@gmail.com>
` Re: Regression: partial index with IS NOT NULL predicate not used for min/max optimization on NOT NULL columns
2025-12-24 17:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Regression: partial index with IS NOT NULL predicate not used for min/max optimization on NOT NULL columns
2025-12-24 18:43 UTC Dmytro Astapov <dastapov@gmail.com>
[3+ messages in thread]
BUG #19359: Row level security: Upserts require insert policies in the update path
2025-12-18 15:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19359: Row level security: Upserts require insert policies in the update path
2025-12-19 17:40 UTC Srinath Reddy Sadipiralla <srinath2133@gmail.com>
` Re: BUG #19359: Row level security: Upserts require insert policies in the update path
2025-12-19 23:12 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
[3+ messages in thread]
[BUG] PostgreSQL 14.5: Data corruption in table tb_workstation_message (possible fstrim-related on eMMC)
2025-12-18 06:42 UTC =?utf-8?B?56ysMTA45qyh5piO5aSp?= <87326549@qq.com>
` Re: [BUG] PostgreSQL 14.5: Data corruption in table tb_workstation_message (possible fstrim-related on eMMC)
2025-12-18 08:40 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: [BUG] PostgreSQL 14.5: Data corruption in table tb_workstation_message (possible fstrim-related on eMMC)
2025-12-18 13:30 UTC Greg Sabino Mullane <htamfids@gmail.com>
[3+ messages in thread]
BUG #19358: Short circuit optimization exists in generic plan but missed in custom plan
2025-12-17 12:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #19358: Short circuit optimization exists in generic plan but missed in custom plan
2025-12-17 21:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ 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