public inbox for [email protected]
help / color / mirror / Atom feedBUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-05-18 05:06 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-05-20 13:06 UTC Greg Sabino Mullane <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-07 10:53 UTC Hüseyin Demir <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-07 15:51 UTC Tom Lane <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-11 05:49 UTC Hüseyin Demir <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-12 16:22 UTC Hüseyin Demir <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-19 06:25 UTC Hüseyin Demir <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-19 07:40 UTC Hüseyin Demir <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-20 21:53 UTC Laurenz Albe <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-21 05:47 UTC Laurenz Albe <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-22 05:44 UTC Hüseyin Demir <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-22 06:07 UTC Hüseyin Demir <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-22 17:23 UTC Laurenz Albe <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-22 18:30 UTC Tom Lane <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-23 08:32 UTC Hüseyin Demir <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-24 06:14 UTC Hüseyin Demir <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-24 09:56 UTC Laurenz Albe <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-24 12:19 UTC Hüseyin Demir <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-24 14:57 UTC Tom Lane <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-25 07:55 UTC Hüseyin Demir <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-25 10:44 UTC Rui Zhao <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-25 13:53 UTC Tom Lane <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-26 05:18 UTC Laurenz Albe <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-26 06:56 UTC Hüseyin Demir <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-06-26 08:30 UTC Laurenz Albe <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-07-02 21:09 UTC Laurenz Albe <[email protected]>
` Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table
2026-07-10 07:00 UTC Hüseyin Demir <[email protected]>
[27+ messages in thread]
Re: BUG #19523: psql tab-completion shadows pg_db_role_setting
2026-07-09 10:13 UTC Vismay Tiwari <[email protected]>
` Re: BUG #19523: psql tab-completion shadows pg_db_role_setting
2026-07-10 04:49 UTC Kirill Reshke <[email protected]>
` Re: BUG #19523: psql tab-completion shadows pg_db_role_setting
2026-07-10 05:51 UTC Vismay Tiwari <[email protected]>
[3+ messages in thread]
REVOKE's CASCADE protection doesn't work with INHERITed table owners
2026-06-24 21:57 UTC Jacob Champion <[email protected]>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
2026-06-26 00:12 UTC Jacob Champion <[email protected]>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
2026-07-06 11:03 UTC Ayush Tiwari <[email protected]>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
2026-07-08 22:54 UTC Jacob Champion <[email protected]>
` Re: REVOKE's CASCADE protection doesn't work with INHERITed table owners
2026-07-09 14:48 UTC Ayush Tiwari <[email protected]>
[5+ messages in thread]
BUG #19523: psql tab-completion shadows pg_db_role_setting
2026-06-18 07:06 UTC PG Bug reporting form <[email protected]>
` [PATCH v1] psql: schema-qualify catalog references in a tab-completion query
2026-07-09 12:23 UTC Vismay Tiwari <[email protected]>
[2+ messages in thread]
BUG #19519: REPACK can fail due to missing chunk for toast value
2026-06-14 07:00 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-06-17 17:03 UTC Srinath Reddy Sadipiralla <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-03 06:45 UTC Imran Zaheer <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-06 06:36 UTC Michael Paquier <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-06 13:38 UTC Konstantin Knizhnik <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-06 18:00 UTC Alexander Lakhin <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-06 18:21 UTC Matthias van de Meent <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-06 23:18 UTC Michael Paquier <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-06 23:51 UTC Matthias van de Meent <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-07 01:42 UTC Michael Paquier <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-07 05:21 UTC Michael Paquier <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-07 17:10 UTC Srinath Reddy Sadipiralla <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-07 22:15 UTC Michael Paquier <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-08 01:10 UTC Michael Paquier <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-08 12:00 UTC Heikki Linnakangas <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-08 15:00 UTC Imran Zaheer <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-08 22:49 UTC Michael Paquier <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-09 02:47 UTC Michael Paquier <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-09 05:17 UTC Konstantin Knizhnik <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-09 05:43 UTC Michael Paquier <[email protected]>
` Re: BUG #19519: REPACK can fail due to missing chunk for toast value
2026-07-09 10:08 UTC Konstantin Knizhnik <[email protected]>
[21+ messages in thread]
Re: BUG #19507: Auto-named partition table constraint conflicts
2026-07-09 09:15 UTC Vismay Tiwari <[email protected]>
` Re: BUG #19507: Auto-named partition table constraint conflicts
2026-07-09 09:31 UTC Vismay Tiwari <[email protected]>
[2+ messages in thread]
BUG #19549: Physical replication slot xmin value stuck
2026-07-09 08:57 UTC PG Bug reporting form <[email protected]>
BUG #19545: Integer truncation of `GinTuple.keylen` causes out-of-bounds read in parallel GIN index build
2026-07-07 14:13 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19545: Integer truncation of `GinTuple.keylen` causes out-of-bounds read in parallel GIN index build
2026-07-08 06:27 UTC Ewan Young <[email protected]>
` Re: BUG #19545: Integer truncation of `GinTuple.keylen` causes out-of-bounds read in parallel GIN index build
2026-07-08 07:52 UTC Heikki Linnakangas <[email protected]>
` Re: BUG #19545: Integer truncation of `GinTuple.keylen` causes out-of-bounds read in parallel GIN index build
2026-07-08 11:34 UTC Ewan Young <[email protected]>
` Re: BUG #19545: Integer truncation of `GinTuple.keylen` causes out-of-bounds read in parallel GIN index build
2026-07-08 14:36 UTC Heikki Linnakangas <[email protected]>
` Re: BUG #19545: Integer truncation of `GinTuple.keylen` causes out-of-bounds read in parallel GIN index build
2026-07-08 17:14 UTC Peter Eisentraut <[email protected]>
` Re: BUG #19545: Integer truncation of `GinTuple.keylen` causes out-of-bounds read in parallel GIN index build
2026-07-09 05:16 UTC Ewan Young <[email protected]>
` Re: BUG #19545: Integer truncation of `GinTuple.keylen` causes out-of-bounds read in parallel GIN index build
2026-07-09 05:28 UTC Tom Lane <[email protected]>
` Re: BUG #19545: Integer truncation of `GinTuple.keylen` causes out-of-bounds read in parallel GIN index build
2026-07-09 08:32 UTC Ewan Young <[email protected]>
[9+ messages in thread]
BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-06-24 15:22 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-06-27 19:22 UTC Bharath Rupireddy <[email protected]>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-06-28 09:59 UTC Dean Rasheed <[email protected]>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-06-28 23:34 UTC Bharath Rupireddy <[email protected]>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-06-30 08:35 UTC Dean Rasheed <[email protected]>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-07-07 07:38 UTC Bharath Rupireddy <[email protected]>
` Re: BUG #19536: UPDATE RETURNING OLD value is stale after concurrent update when table has a BEFORE UPDATE trigger
2026-07-08 20:29 UTC Dean Rasheed <[email protected]>
[7+ messages in thread]
BUG #19544: PostgreSQL 18.3 backend crashes with SIGSEGV when a PL/pgSQL function
2026-07-06 13:49 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19544: PostgreSQL 18.3 backend crashes with SIGSEGV when a PL/pgSQL function
2026-07-06 17:01 UTC Ayush Tiwari <[email protected]>
` Re: BUG #19544: PostgreSQL 18.3 backend crashes with SIGSEGV when a PL/pgSQL function
2026-07-08 18:25 UTC surya poondla <[email protected]>
[3+ messages in thread]
BUG #19548: Missing dependency between a graph edge and the related PK
2026-07-08 14:44 UTC PG Bug reporting form <[email protected]>
BUG #19547: `libpqrcv_create_slot` dereferences NULL on a malformed `CREATE_REPLICATION_SLOT` reply (just a sugg
2026-07-08 12:15 UTC PG Bug reporting form <[email protected]>
BUG #19542: Boolean syntax in GRAPH_TABLE
2026-07-03 13:25 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19542: Boolean syntax in GRAPH_TABLE
2026-07-05 08:20 UTC vaibhave postgres <[email protected]>
` Re: BUG #19542: Boolean syntax in GRAPH_TABLE
2026-07-08 07:51 UTC Peter Eisentraut <[email protected]>
[3+ messages in thread]
EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-02 16:58 UTC Thom Brown <[email protected]>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-02 22:10 UTC Richard Guo <[email protected]>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-03 03:06 UTC Richard Guo <[email protected]>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-03 08:36 UTC Thom Brown <[email protected]>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-06 02:17 UTC Richard Guo <[email protected]>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-07 13:49 UTC Thom Brown <[email protected]>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-07 14:20 UTC Thom Brown <[email protected]>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-08 00:08 UTC Richard Guo <[email protected]>
` Re: EXPLAIN (VERBOSE) fails with for JSON_ARRAYAGG/JSON_OBJECTAGG + window function
2026-07-08 00:42 UTC Thom Brown <[email protected]>
[9+ messages in thread]
Re: BUG #19382: Server crash at __nss_database_lookup
2026-03-19 05:00 UTC surya poondla <[email protected]>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-03-19 07:53 UTC =?utf-8?B?c29uZ2ppbnpob3U=?= <[email protected]>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-03-20 18:16 UTC surya poondla <[email protected]>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-02 11:18 UTC Andrey Borodin <[email protected]>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-02 23:14 UTC surya poondla <[email protected]>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-04 12:42 UTC Andrey Borodin <[email protected]>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-09 04:24 UTC surya poondla <[email protected]>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-14 23:49 UTC surya poondla <[email protected]>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-16 12:00 UTC Andrey Borodin <[email protected]>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-16 23:20 UTC surya poondla <[email protected]>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-17 06:57 UTC Andrey Borodin <[email protected]>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-04-23 04:17 UTC surya poondla <[email protected]>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-06-02 23:44 UTC surya poondla <[email protected]>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-06-30 20:50 UTC surya poondla <[email protected]>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-07-06 22:16 UTC Zsolt Parragi <[email protected]>
` Re: BUG #19382: Server crash at __nss_database_lookup
2026-07-07 23:20 UTC surya poondla <[email protected]>
[16+ messages in thread]
BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-06-24 14:41 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-06-27 16:53 UTC Chengpeng Yan <[email protected]>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-06-29 00:39 UTC Richard Guo <[email protected]>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-06-29 13:44 UTC David Rowley <[email protected]>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-03 03:38 UTC David Rowley <[email protected]>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-03 09:09 UTC John Naylor <[email protected]>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-03 09:11 UTC John Naylor <[email protected]>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-03 23:57 UTC David Rowley <[email protected]>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-05 10:44 UTC John Naylor <[email protected]>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-05 12:54 UTC Chengpeng Yan <[email protected]>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-06 07:24 UTC David Rowley <[email protected]>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-06 08:31 UTC Chengpeng Yan <[email protected]>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-07 05:11 UTC John Naylor <[email protected]>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-07 05:35 UTC David Rowley <[email protected]>
` Re: BUG #19533: Wrong results from WindowAgg run-condition pushdown on count() with EXCLUDE CURRENT ROW
2026-07-07 12:02 UTC David Rowley <[email protected]>
[15+ messages in thread]
BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-03 22:21 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-05 04:27 UTC Ayush Tiwari <[email protected]>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-05 04:34 UTC Gabriele Bartolini <[email protected]>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-05 04:39 UTC Ayush Tiwari <[email protected]>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-05 12:12 UTC Matheus Alcantara <[email protected]>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-06-24 09:47 UTC Gabriele Bartolini <[email protected]>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-07-07 01:37 UTC Gabriele Bartolini <[email protected]>
` Re: BUG #19506: LOAD '$libdir/...' inside extension scripts ignores dynamic_library_path with extension_control_path
2026-07-07 10:02 UTC Matheus Alcantara <[email protected]>
[8+ messages in thread]
BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2025-04-04 03:05 UTC PG Bug reporting form <[email protected]>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-06-11 03:31 UTC Fujii Masao <[email protected]>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-06-11 04:29 UTC TAKATSUKA Haruka <[email protected]>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-07-01 14:30 UTC Fujii Masao <[email protected]>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-07-03 02:25 UTC Fujii Masao <[email protected]>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-07-06 17:22 UTC Robert Haas <[email protected]>
` Re: BUG #18876: HINT messages for mxid wrap-around say "drop stale slots", but that may not be appropriate
2026-07-06 23:22 UTC Fujii Masao <[email protected]>
[7+ messages in thread]
BUG #19525: In `contrib/dict_int`, handling a token whose first byte is a null byte causes `pnstrdup()` .
2026-06-18 07:54 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19525: In `contrib/dict_int`, handling a token whose first byte is a null byte causes `pnstrdup()` .
2026-06-18 14:41 UTC Ayush Tiwari <[email protected]>
` Re: BUG #19525: In `contrib/dict_int`, handling a token whose first byte is a null byte causes `pnstrdup()` .
2026-06-18 18:19 UTC 王跃林 <[email protected]>
` Re: BUG #19525: In `contrib/dict_int`, handling a token whose first byte is a null byte causes `pnstrdup()` .
2026-07-05 20:12 UTC Tom Lane <[email protected]>
[4+ messages in thread]
BUG #19543: ALTER RULE ... RENAME accepts reserved name "_RETURN" for a non-view rule; breaks a restored dump
2026-07-03 23:26 UTC PG Bug reporting form <[email protected]>
` Re: BUG #19543: ALTER RULE ... RENAME accepts reserved name "_RETURN" for a non-view rule; breaks a restored dump
2026-07-04 14:37 UTC Tom Lane <[email protected]>
[2+ messages in thread]
Re: uuidv7 improperly accepts dates before 1970-01-01
2026-04-27 22:51 UTC Christophe Pettus <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-05-28 00:02 UTC Masahiko Sawada <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-05-28 01:00 UTC Baji Shaik <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-11 19:20 UTC Masahiko Sawada <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-12 22:34 UTC Baji Shaik <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-24 15:25 UTC Baji Shaik <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-24 17:46 UTC Masahiko Sawada <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-24 17:58 UTC Tristan Partin <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-24 20:02 UTC Christophe Pettus <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-24 20:31 UTC Zsolt Parragi <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-24 23:22 UTC Baji Shaik <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-25 02:19 UTC Kyotaro Horiguchi <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-25 13:47 UTC Baji Shaik <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-26 04:57 UTC Kyotaro Horiguchi <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-06-29 23:18 UTC Masahiko Sawada <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-07-03 16:34 UTC Baji Shaik <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-07-03 19:54 UTC Zsolt Parragi <[email protected]>
` Re: uuidv7 improperly accepts dates before 1970-01-01
2026-07-03 23:54 UTC Baji Shaik <[email protected]>
[18+ messages in thread]
Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-06-16 11:29 UTC 王跃林 <[email protected]>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-06-17 19:19 UTC Ayush Tiwari <[email protected]>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-06-18 05:24 UTC 王跃林 <[email protected]>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-02 14:38 UTC Tom Lane <[email protected]>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-02 15:43 UTC Ayush Tiwari <[email protected]>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-02 16:54 UTC Tom Lane <[email protected]>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-02 17:46 UTC Ayush Tiwari <[email protected]>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-02 23:02 UTC Tom Lane <[email protected]>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-03 08:40 UTC Ayush Tiwari <[email protected]>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-03 13:50 UTC Tom Lane <[email protected]>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-03 16:48 UTC Ayush Tiwari <[email protected]>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-03 17:01 UTC Tom Lane <[email protected]>
` Re: Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints
2026-07-03 19:36 UTC Tom Lane <[email protected]>
[13+ messages in thread]
BTree index corruption (heap-tid-past-end, unexpected zero page, misplaced TID in posting list) recurring on high-churn tables, PG 18.3, data_checksums=on, no preceding crash
2026-07-01 08:12 UTC Alessandro Regolini <[email protected]>
` Re: BTree index corruption (heap-tid-past-end, unexpected zero page, misplaced TID in posting list) recurring on high-churn tables, PG 18.3, data_checksums=on, no preceding crash
2026-07-02 18:32 UTC Peter Geoghegan <[email protected]>
[2+ messages in thread]
Autoprewarm workers terminated due to a segmentation fault
2026-06-09 18:37 UTC Glauber Batista <[email protected]>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-09 21:06 UTC Matheus Alcantara <[email protected]>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-09 21:44 UTC Tomas Vondra <[email protected]>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-09 22:25 UTC Matheus Alcantara <[email protected]>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-11 14:40 UTC Tomas Vondra <[email protected]>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-15 14:35 UTC Melanie Plageman <[email protected]>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-26 17:55 UTC Tomas Vondra <[email protected]>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-26 18:07 UTC Matheus Alcantara <[email protected]>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-06-29 15:12 UTC Melanie Plageman <[email protected]>
` Re: Autoprewarm workers terminated due to a segmentation fault
2026-07-01 19:16 UTC Glauber Batista <[email protected]>
[10+ messages in thread]
BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-06-28 02:14 UTC Bill Kim <[email protected]>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-06-28 18:54 UTC Daniel Gustafsson <[email protected]>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-06-29 12:04 UTC Bill Kim <[email protected]>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-06-29 15:04 UTC Tom Lane <[email protected]>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-06-29 15:27 UTC Bill Kim <[email protected]>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-06-29 15:35 UTC Tom Lane <[email protected]>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-06-29 15:50 UTC Bill Kim <[email protected]>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-06-29 23:08 UTC Tom Lane <[email protected]>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-07-01 13:38 UTC Bill Kim <[email protected]>
` Re: BUG #19524: NaN handling in btree_gist's float4/float8 opclasses
2026-07-01 17:33 UTC Tom Lane <[email protected]>
[10+ 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