pg.ddx.io pgsql-bugs@postgresql.org mailing list archivehelp / color / mirror / Atom feed
3. PostgreSQL Server Subprocess Went down at function 'load_critical_index' and the Client Cannot Connect to the Database 2023-04-13 16:35 UTC fjz22@mails.tsinghua.edu.cn 2. PostgreSQL Server Subprocess Went down at function 'datumTransfer' 2023-04-13 16:28 UTC fjz22@mails.tsinghua.edu.cn BUG #17892: Bug primary key 2023-04-12 10:30 UTC PG Bug reporting form <noreply@postgresql.org> ` Re: BUG #17892: Bug primary key 2023-04-12 12:03 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #17892: Bug primary key 2023-04-12 22:02 UTC Michael Paquier <michael@paquier.xyz> ` Re: BUG #17892: Bug primary key 2023-04-12 22:13 UTC Peter Geoghegan <pg@bowt.ie> ` Re: BUG #17892: Bug primary key 2023-04-13 15:18 UTC Alvaro Herrera <alvherre@alvh.no-ip.org> [5+ messages in thread] Error while installing Postgresql 2023-04-05 21:44 UTC Edi Keškić <edi.keskic97vk@gmail.com> ` Re: Error while installing Postgresql 2023-04-13 05:42 UTC Manika Singhal <manika.singhal@enterprisedb.com> ` Re: Error while installing Postgresql 2023-04-13 08:41 UTC Edi Keškić <edi.keskic97vk@gmail.com> ` Re: Error while installing Postgresql 2023-04-13 11:09 UTC Manika Singhal <manika.singhal@enterprisedb.com> ` Re: Error while installing Postgresql 2023-04-13 12:50 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com> ` Error while installing Postgresql 2023-04-13 14:57 UTC Wetmore, Matthew (CTR) <Matthew.Wetmore@express-scripts.com> [6+ messages in thread] Unlimited memory consumption with long-lived connection 2023-02-21 12:57 UTC Duncan Sands <duncan.sands@deepbluecap.com> ` Re: Unlimited memory consumption with long-lived connection 2023-02-21 14:32 UTC Heikki Linnakangas <hlinnaka@iki.fi> ` Re: Unlimited memory consumption with long-lived connection 2023-02-22 14:53 UTC Justin Pryzby <pryzby@telsasoft.com> ` Re: Unlimited memory consumption with long-lived connection 2023-02-22 17:10 UTC Duncan Sands <duncan.sands@deepbluecap.com> ` Re: Unlimited memory consumption with long-lived connection 2023-02-22 18:28 UTC Andres Freund <andres@anarazel.de> ` Re: Unlimited memory consumption with long-lived connection 2023-02-22 19:12 UTC Justin Pryzby <pryzby@telsasoft.com> ` Re: Unlimited memory consumption with long-lived connection 2023-04-12 17:52 UTC Justin Pryzby <pryzby@telsasoft.com> [7+ messages in thread] BUG #17862: Overall query cost ignores window function 2023-03-22 17:42 UTC PG Bug reporting form <noreply@postgresql.org> ` Re: BUG #17862: Overall query cost ignores window function 2023-03-22 21:03 UTC David Rowley <dgrowleyml@gmail.com> ` Re: BUG #17862: Overall query cost ignores window function 2023-03-23 14:40 UTC Tim Palmer <tim3sp@gmail.com> ` Re: BUG #17862: Overall query cost ignores window function 2023-03-25 01:40 UTC David Rowley <dgrowleyml@gmail.com> ` Re: BUG #17862: Overall query cost ignores window function 2023-04-12 09:05 UTC David Rowley <dgrowleyml@gmail.com> [5+ messages in thread] ERROR: no NOT NULL constraint found to drop 2023-04-10 07:16 UTC Richard Guo <guofenglinux@gmail.com> ` Re: ERROR: no NOT NULL constraint found to drop 2023-04-10 07:55 UTC Michael Paquier <michael@paquier.xyz> ` Re: ERROR: no NOT NULL constraint found to drop 2023-04-10 13:46 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: ERROR: no NOT NULL constraint found to drop 2023-04-12 00:31 UTC Michael Paquier <michael@paquier.xyz> [4+ messages in thread] BUG #17891: MAIF - Strange behavior on Grants with Groups 2023-04-12 00:23 UTC PG Bug reporting form <noreply@postgresql.org> Incorrect number of rows inserted into partitioned table 2023-04-10 18:42 UTC Роман Осипов <osipovromanvladimirovich@gmail.com> ` Re: Incorrect number of rows inserted into partitioned table 2023-04-10 21:36 UTC David Rowley <dgrowleyml@gmail.com> ` Re: Incorrect number of rows inserted into partitioned table 2023-04-10 21:39 UTC Tomas Vondra <tomas.vondra@enterprisedb.com> ` Re: Incorrect number of rows inserted into partitioned table 2023-04-10 21:58 UTC Роман Осипов <osipovromanvladimirovich@gmail.com> ` Re: Incorrect number of rows inserted into partitioned table 2023-04-10 22:04 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: Incorrect number of rows inserted into partitioned table 2023-04-11 05:48 UTC Роман Осипов <osipovromanvladimirovich@gmail.com> [6+ messages in thread] BUG #17866: behavior does not match documentation 2023-03-23 15:10 UTC PG Bug reporting form <noreply@postgresql.org> ` Re: BUG #17866: behavior does not match documentation 2023-03-23 18:31 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #17866: behavior does not match documentation 2023-03-23 21:25 UTC Daniel Gustafsson <daniel@yesql.se> ` Re: BUG #17866: behavior does not match documentation 2023-03-23 21:54 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #17866: behavior does not match documentation 2023-03-23 22:00 UTC Daniel Gustafsson <daniel@yesql.se> ` Re: BUG #17866: behavior does not match documentation 2023-04-10 17:11 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #17866: behavior does not match documentation 2023-04-10 18:33 UTC Daniel Gustafsson <daniel@yesql.se> [7+ messages in thread] Need assistance in performance tuning of a particular query 2023-04-07 16:46 UTC Shikha, Kumari - Dell Team <Kumari.Shikha@dellteam.com> ` Re: Need assistance in performance tuning of a particular query 2023-04-07 17:36 UTC Tom Lane <tgl@sss.pgh.pa.us> [2+ messages in thread] Test mail for pgsql-admin 2023-04-07 16:45 UTC Shikha, Kumari - Dell Team <Kumari.Shikha@dellteam.com> Wrong results with postgres_fdw and merge anti join from RHEL 7.9 to RHEL 8.7 2023-04-05 18:33 UTC Daniel Westermann (DWE) <daniel.westermann@dbi-services.com> ` Re: Wrong results with postgres_fdw and merge anti join from RHEL 7.9 to RHEL 8.7 2023-04-05 18:41 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: Wrong results with postgres_fdw and merge anti join from RHEL 7.9 to RHEL 8.7 2023-04-05 18:51 UTC Daniel Westermann (DWE) <daniel.westermann@dbi-services.com> ` Re: Wrong results with postgres_fdw and merge anti join from RHEL 7.9 to RHEL 8.7 2023-04-05 19:04 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: Wrong results with postgres_fdw and merge anti join from RHEL 7.9 to RHEL 8.7 2023-04-05 19:20 UTC Daniel Westermann (DWE) <daniel.westermann@dbi-services.com> ` Re: Wrong results with postgres_fdw and merge anti join from RHEL 7.9 to RHEL 8.7 2023-04-05 19:46 UTC Jim Mlodgenski <jimmy76@gmail.com> ` Re: Wrong results with postgres_fdw and merge anti join from RHEL 7.9 to RHEL 8.7 2023-04-05 20:07 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: Wrong results with postgres_fdw and merge anti join from RHEL 7.9 to RHEL 8.7 2023-04-05 20:38 UTC Joe Conway <mail@joeconway.com> ` Re: Wrong results with postgres_fdw and merge anti join from RHEL 7.9 to RHEL 8.7 2023-04-06 05:01 UTC Daniel Westermann (DWE) <daniel.westermann@dbi-services.com> [9+ messages in thread] BUG #17876: Function width_bucket() for float8 input returns value out of range 2023-03-29 08:11 UTC PG Bug reporting form <noreply@postgresql.org> ` Re: BUG #17876: Function width_bucket() for float8 input returns value out of range 2023-03-29 08:18 UTC Mats Kindahl <mats@timescale.com> ` Re: BUG #17876: Function width_bucket() for float8 input returns value out of range 2023-03-29 12:33 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #17876: Function width_bucket() for float8 input returns value out of range 2023-03-30 07:54 UTC Mats Kindahl <mats@timescale.com> ` Re: BUG #17876: Function width_bucket() for float8 input returns value out of range 2023-03-30 15:35 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #17876: Function width_bucket() for float8 input returns value out of range 2023-03-31 09:30 UTC Mats Kindahl <mats@timescale.com> ` Re: BUG #17876: Function width_bucket() for float8 input returns value out of range 2023-03-31 13:14 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #17876: Function width_bucket() for float8 input returns value out of range 2023-04-05 07:58 UTC Mats Kindahl <mats@timescale.com> ` Re: BUG #17876: Function width_bucket() for float8 input returns value out of range 2023-04-05 21:41 UTC Tom Lane <tgl@sss.pgh.pa.us> [9+ messages in thread] BUG #17887: EDB Community Installer for windows, locale selection not working properly 2023-04-05 17:32 UTC PG Bug reporting form <noreply@postgresql.org> BUG #17886: Error disabling user triggers on a partitioned table 2023-04-04 16:47 UTC PG Bug reporting form <noreply@postgresql.org> ` Re: BUG #17886: Error disabling user triggers on a partitioned table 2023-04-04 16:49 UTC jazzl 0013 <jazz001319@gmail.com> ` Re: BUG #17886: Error disabling user triggers on a partitioned table 2023-04-04 18:24 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #17886: Error disabling user triggers on a partitioned table 2023-04-05 07:33 UTC Alvaro Herrera <alvherre@alvh.no-ip.org> ` Re: BUG #17886: Error disabling user triggers on a partitioned table 2023-04-05 16:57 UTC Tom Lane <tgl@sss.pgh.pa.us> [5+ messages in thread] BUG #17885: slow planning constraint_exclusion 2023-04-04 16:38 UTC PG Bug reporting form <noreply@postgresql.org> ` Re: BUG #17885: slow planning constraint_exclusion 2023-04-04 22:16 UTC David Rowley <dgrowleyml@gmail.com> ` Re: BUG #17885: slow planning constraint_exclusion 2023-04-04 22:53 UTC David Rowley <dgrowleyml@gmail.com> ` Re: BUG #17885: slow planning constraint_exclusion 2023-04-05 00:30 UTC Maxim Boguk <maxim.boguk@gmail.com> ` Re: BUG #17885: slow planning constraint_exclusion 2023-04-05 00:45 UTC David Rowley <dgrowleyml@gmail.com> [5+ messages in thread] BUG #17883: Segmentation fault when create brin index on user-defined type. 2023-04-04 05:51 UTC PG Bug reporting form <noreply@postgresql.org> ` Re: BUG #17883: Segmentation fault when create brin index on user-defined type. 2023-04-04 12:38 UTC Tom Lane <tgl@sss.pgh.pa.us> [2+ messages in thread] BUG #17882: I can't disable triggers on a table that has been partitioned 2023-04-02 15:28 UTC PG Bug reporting form <noreply@postgresql.org> ` Re: BUG #17882: I can't disable triggers on a table that has been partitioned 2023-04-02 16:20 UTC Tom Lane <tgl@sss.pgh.pa.us> [2+ messages in thread] BUG #17881: Dependency error in Barman 3.5 2023-03-31 10:11 UTC PG Bug reporting form <noreply@postgresql.org> ` BUG #17881: Dependency error in Barman 3.5 2023-03-31 13:40 UTC David G. Johnston <david.g.johnston@gmail.com> ` Re: BUG #17881: Dependency error in Barman 3.5 **SOLVED** 2023-03-31 22:09 UTC José María Terry Jiménez <jtj@tssystems.net> ` Re: BUG #17881: Dependency error in Barman 3.5 2023-03-31 22:17 UTC José María Terry Jiménez <jtj@tssystems.net> [4+ messages in thread] BUG #17880: Uninitialised value used when analyzing a table with an inheritance tree containing no children 2023-03-31 10:00 UTC PG Bug reporting form <noreply@postgresql.org> ` Re: BUG #17880: Uninitialised value used when analyzing a table with an inheritance tree containing no children 2023-03-31 13:40 UTC Tom Lane <tgl@sss.pgh.pa.us> [2+ messages in thread] BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-27 08:04 UTC PG Bug reporting form <noreply@postgresql.org> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-27 14:53 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-27 21:28 UTC Andres Freund <andres@anarazel.de> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-27 21:38 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-28 02:27 UTC Maxim Boguk <maxim.boguk@gmail.com> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-28 03:05 UTC David Rowley <dgrowleyml@gmail.com> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-28 03:20 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-28 04:54 UTC Maxim Boguk <maxim.boguk@gmail.com> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-28 06:13 UTC David Rowley <dgrowleyml@gmail.com> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-28 06:21 UTC Maxim Boguk <maxim.boguk@gmail.com> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-28 06:28 UTC Maxim Boguk <maxim.boguk@gmail.com> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-28 18:24 UTC Andres Freund <andres@anarazel.de> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-28 18:31 UTC Andres Freund <andres@anarazel.de> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-28 18:33 UTC Andres Freund <andres@anarazel.de> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-28 18:38 UTC Andres Freund <andres@anarazel.de> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-28 22:03 UTC David Rowley <dgrowleyml@gmail.com> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-30 19:50 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time 2023-03-31 12:40 UTC Maxim Boguk <maxim.boguk@gmail.com> [18+ messages in thread] BUG #17879: ERROR: unrecognized node type: 2139062143 2023-03-30 02:36 UTC PG Bug reporting form <noreply@postgresql.org> ` Re: BUG #17879: ERROR: unrecognized node type: 2139062143 2023-03-30 10:54 UTC David Rowley <dgrowleyml@gmail.com> ` Re: BUG #17879: ERROR: unrecognized node type: 2139062143 2023-03-30 23:19 UTC David Rowley <dgrowleyml@gmail.com> [3+ messages in thread] BUG #17877: Referencing a system column in a foreign key leads to incorrect memory access 2023-03-29 14:00 UTC PG Bug reporting form <noreply@postgresql.org> ` Re: BUG #17877: Referencing a system column in a foreign key leads to incorrect memory access 2023-03-29 16:12 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #17877: Referencing a system column in a foreign key leads to incorrect memory access 2023-03-30 09:57 UTC Alvaro Herrera <alvherre@alvh.no-ip.org> ` Re: BUG #17877: Referencing a system column in a foreign key leads to incorrect memory access 2023-03-30 17:33 UTC Tom Lane <tgl@sss.pgh.pa.us> [4+ messages in thread] BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2020-03-29 21:00 UTC PG Bug reporting form <noreply@postgresql.org> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2020-03-30 05:00 UTC Alexander Lakhin <exclusion@gmail.com> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2020-04-06 06:00 UTC Alexander Lakhin <exclusion@gmail.com> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2020-05-02 04:45 UTC Alexander Lakhin <exclusion@gmail.com> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2020-05-05 18:59 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2020-05-11 20:00 UTC Alexander Lakhin <exclusion@gmail.com> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2020-05-12 05:00 UTC Alexander Lakhin <exclusion@gmail.com> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2020-10-12 12:30 UTC Pavel Borisov <pashkin.elfe@gmail.com> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2020-10-12 16:03 UTC Pavel Borisov <pashkin.elfe@gmail.com> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2020-10-12 20:03 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2020-10-12 22:16 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2020-10-22 05:50 UTC Andrey Borodin <x4mmm@yandex-team.ru> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2020-10-22 14:01 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2020-10-24 16:40 UTC Andrey Borodin <x4mmm@yandex-team.ru> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2020-11-02 16:55 UTC Pavel Borisov <pashkin.elfe@gmail.com> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2023-03-29 15:37 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2023-03-29 22:21 UTC Tom Lane <tgl@sss.pgh.pa.us> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2023-03-30 04:42 UTC Noah Misch <noah@leadboat.com> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2023-03-30 05:00 UTC Alexander Lakhin <exclusion@gmail.com> ` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering 2023-03-30 11:47 UTC Tom Lane <tgl@sss.pgh.pa.us> [20+ 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