pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedPostgreSQL 12.15 query performance problem
2023-09-12 21:25 UTC Ринат Мухтаров <r.mukhtarov@rabota.ru>
"as name" is shadowed by name "value" when selecting with "left join jsonb_array_elements(d.items) as item on true"
2023-09-12 16:59 UTC Aleksandr Vinokurov <aleksandr.vin@gmail.com>
` Re: "as name" is shadowed by name "value" when selecting with "left join jsonb_array_elements(d.items) as item on true"
2023-09-12 17:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: "as name" is shadowed by name "value" when selecting with "left join jsonb_array_elements(d.items) as item on true"
2023-09-12 19:03 UTC Aleksandr Vinokurov <aleksandr.vin@gmail.com>
[3+ messages in thread]
BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-14 16:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-14 17:03 UTC ocean_li_996 <ocean_li_996@163.com>
` Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-17 03:24 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-17 06:51 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-17 10:03 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-17 10:07 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-17 12:10 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-17 14:03 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-18 04:21 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re:RE: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-20 16:51 UTC ocean_li_996 <ocean_li_996@163.com>
` Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-20 21:05 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-21 12:41 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-21 13:37 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-21 18:19 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-21 18:27 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-23 08:46 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-25 04:06 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` RE: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-08-28 05:39 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-09-05 11:31 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-09-07 12:10 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-09-09 11:39 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18055: logical decoding core on AllocateSnapshotBuilder()
2023-09-12 10:09 UTC Amit Kapila <amit.kapila16@gmail.com>
[22+ messages in thread]
BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-06-13 23:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-06-14 21:37 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-06-14 21:57 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-06-14 22:30 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-06-15 20:35 UTC Will Mortensen <will@extrahop.com>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-06-16 01:01 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-06-16 01:36 UTC Will Mortensen <will@extrahop.com>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-06-16 01:58 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-06-19 17:45 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-06-20 06:41 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-06-21 03:59 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-08-11 21:15 UTC Jacob Speidel <jacob@extrahop.com>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-08-12 00:23 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-08-12 00:48 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-08-14 00:11 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-09-01 01:08 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-09-01 02:56 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-09-01 03:31 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-09-01 15:20 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-09-02 00:08 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-09-02 15:21 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-09-03 23:09 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-09-04 01:55 UTC Will Mortensen <will@extrahop.com>
` Re: BUG #17973: Reinit of pgstats entry for dropped DB can break autovacuum daemon
2023-09-12 02:11 UTC Andres Freund <andres@anarazel.de>
[24+ messages in thread]
BUG #18105: ogr_fdw_15 incompatible with latest gdal36-libs
2023-09-11 14:55 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18105: ogr_fdw_15 incompatible with latest gdal36-libs
2023-09-11 17:25 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
BUG #18101: 'RAISE LOG ...' with omitted trailing ';' does not throw syntax error in certain situations
2023-09-09 02:29 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18101: 'RAISE LOG ...' with omitted trailing ';' does not throw syntax error in certain situations
2023-09-09 20:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18099: ERROR: could not access status of transaction 4007513275
2023-09-08 06:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18099: ERROR: could not access status of transaction 4007513275
2023-09-08 15:18 UTC Carlos Alves <carlos.alves@tecnisys.com.br>
` Re: BUG #18099: ERROR: could not access status of transaction 4007513275
2023-09-08 17:45 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[3+ messages in thread]
BUG #18094: max max_connections cannot be set
2023-09-07 15:56 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18094: max max_connections cannot be set
2023-09-07 16:07 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18094: max max_connections cannot be set
2023-09-07 16:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18094: max max_connections cannot be set
2023-09-08 04:25 UTC Nikolay Samokhvalov <nikolay@samokhvalov.com>
` Re: BUG #18094: max max_connections cannot be set
2023-09-08 04:55 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18094: max max_connections cannot be set
2023-09-08 13:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18094: max max_connections cannot be set
2023-09-08 14:04 UTC Nikolay Samokhvalov <nikolay@samokhvalov.com>
` Re: BUG #18094: max max_connections cannot be set
2023-09-08 15:25 UTC David G. Johnston <david.g.johnston@gmail.com>
[8+ messages in thread]
BUG #18095: Unintended non-SSL connection attempt by psql cli command after a failed password authentication
2023-09-07 16:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18095: Unintended non-SSL connection attempt by psql cli command after a failed password authentication
2023-09-07 17:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18095: Unintended non-SSL connection attempt by psql cli command after a failed password authentication
2023-09-07 20:50 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[3+ messages in thread]
BUG #18092: Unexpected Result by enable_seqscan
2023-09-07 05:52 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18092: Unexpected Result by enable_seqscan
2023-09-07 07:35 UTC Francisco Olarte <folarte@peoplecall.com>
` Re: BUG #18092: Unexpected Result by enable_seqscan
2023-09-07 11:05 UTC David Rowley <dgrowleyml@gmail.com>
[3+ messages in thread]
BUG #18091: Unexpected Result by enable_material
2023-09-07 05:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18091: Unexpected Result by enable_material
2023-09-07 07:30 UTC Francisco Olarte <folarte@peoplecall.com>
` Re: BUG #18091: Unexpected Result by enable_material
2023-09-07 07:51 UTC Richard Guo <guofenglinux@gmail.com>
[3+ messages in thread]
BUG #18084: Count Mismatch Challenges During PostgreSQL Database Migration: Causes and Solutions
2023-09-04 17:55 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18084: Count Mismatch Challenges During PostgreSQL Database Migration: Causes and Solutions
2023-09-04 21:12 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18084: Count Mismatch Challenges During PostgreSQL Database Migration: Causes and Solutions
2023-09-05 15:18 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18084: Count Mismatch Challenges During PostgreSQL Database Migration: Causes and Solutions
2023-09-06 17:40 UTC Git Queries <gitqueries0@gmail.com>
` Re: BUG #18084: Count Mismatch Challenges During PostgreSQL Database Migration: Causes and Solutions
2023-09-06 17:41 UTC Git Queries <gitqueries0@gmail.com>
` Re: BUG #18084: Count Mismatch Challenges During PostgreSQL Database Migration: Causes and Solutions
2023-09-06 18:02 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18084: Count Mismatch Challenges During PostgreSQL Database Migration: Causes and Solutions
2023-09-07 00:26 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18084: Count Mismatch Challenges During PostgreSQL Database Migration: Causes and Solutions
2023-09-07 01:00 UTC Bruce Momjian <bruce@momjian.us>
[8+ messages in thread]
BUG #18090: Encountering Toast Table Corruption and Missing Chunk Number Error During PostgreSQL Data Migration
2023-09-05 20:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18090: Encountering Toast Table Corruption and Missing Chunk Number Error During PostgreSQL Data Migration
2023-09-06 08:08 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
BUG #18089: Orphaned Rows During PostgreSQL Data Migration
2023-09-05 13:22 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18089: Orphaned Rows During PostgreSQL Data Migration
2023-09-06 04:13 UTC David Rowley <dgrowleyml@gmail.com>
[2+ messages in thread]
pg_dump assertion failure with "-n pg_catalog"
2023-06-07 17:36 UTC Jeff Davis <pgsql@j-davis.com>
` Re: pg_dump assertion failure with "-n pg_catalog"
2023-06-12 06:52 UTC Michael Paquier <michael@paquier.xyz>
` Re: pg_dump assertion failure with "-n pg_catalog"
2023-06-15 22:47 UTC Jeff Davis <pgsql@j-davis.com>
` Re: pg_dump assertion failure with "-n pg_catalog"
2023-06-16 05:29 UTC Michael Paquier <michael@paquier.xyz>
` Re: pg_dump assertion failure with "-n pg_catalog"
2023-06-16 17:29 UTC Jeff Davis <pgsql@j-davis.com>
` Re: pg_dump assertion failure with "-n pg_catalog"
2023-08-22 20:10 UTC Jeff Davis <pgsql@j-davis.com>
` Re: pg_dump assertion failure with "-n pg_catalog"
2023-09-05 09:45 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: pg_dump assertion failure with "-n pg_catalog"
2023-09-05 22:33 UTC Jeff Davis <pgsql@j-davis.com>
[8+ messages in thread]
BUG #18088: Table Corruption Issues Arising from Abrupt Server Shutdown During PostgreSQL 10.20 to 14.7 Migratio
2023-09-05 13:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18088: Table Corruption Issues Arising from Abrupt Server Shutdown During PostgreSQL 10.20 to 14.7 Migratio
2023-09-05 17:44 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18086: compilation failed due to epoll_create1 not present
2023-09-05 10:59 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18086: compilation failed due to epoll_create1 not present
2023-09-05 11:51 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18086: compilation failed due to epoll_create1 not present
2023-09-05 13:26 UTC Duke Astar <dukeastar@gmail.com>
[3+ messages in thread]
BUG #18085: Error in documentation
2023-09-05 09:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18085: Error in documentation
2023-09-05 13:14 UTC Daniel Gustafsson <daniel@yesql.se>
[2+ messages in thread]
BUG #18087: pg_visibility: false positives in pg_check_visible
2023-09-05 13:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18087: pg_visibility: false positives in pg_check_visible
2023-09-05 13:12 UTC huyajun <hu_yajun@qq.com>
[2+ messages in thread]
BUG #18083: not compile PostgreSQL module in Qt with GCC 11.2 compiler
2023-09-04 17:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18083: not compile PostgreSQL module in Qt with GCC 11.2 compiler
2023-09-05 01:51 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18083: not compile PostgreSQL module in Qt with GCC 11.2 compiler
2023-09-05 02:25 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18083: not compile PostgreSQL module in Qt with GCC 11.2 compiler
2023-09-05 08:57 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18083: not compile PostgreSQL module in Qt with GCC 11.2 compiler
2023-09-05 09:52 UTC Navadvipa Chandra das <navadvipa.chandra.das@nizhnyaya-navadvipa.ru>
` Re: BUG #18083: not compile PostgreSQL module in Qt with GCC 11.2 compiler
2023-09-05 12:55 UTC Daniel Gustafsson <daniel@yesql.se>
[6+ messages in thread]
BUG #18081: Spurious "function with OID ###### does not exist" error
2023-09-04 09:12 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18081: Spurious "function with OID ###### does not exist" error
2023-09-04 15:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18081: Spurious "function with OID ###### does not exist" error
2023-09-05 11:57 UTC Branko Radovanovic <branko.radovanovic.zg@gmail.com>
[3+ messages in thread]
BUG #18082: coredump during initdb
2023-09-04 14:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18082: coredump during initdb
2023-09-04 15:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18082: coredump during initdb
2023-09-05 07:33 UTC Duke Astar <dukeastar@gmail.com>
` Re: BUG #18082: coredump during initdb
2023-09-05 10:21 UTC John Naylor <john.naylor@enterprisedb.com>
` Re: BUG #18082: coredump during initdb
2023-09-05 11:01 UTC Duke Astar <dukeastar@gmail.com>
[5+ messages in thread]
BUG #17950: Incorrect memory access in gtsvector_picksplit()
2023-05-29 20:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17950: Incorrect memory access in gtsvector_picksplit()
2023-06-17 14:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17950: Incorrect memory access in gtsvector_picksplit()
2023-08-13 13:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17950: Incorrect memory access in gtsvector_picksplit()
2023-08-13 14:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17950: Incorrect memory access in gtsvector_picksplit()
2023-08-13 18:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17950: Incorrect memory access in gtsvector_picksplit()
2023-09-04 06:35 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17950: Incorrect memory access in gtsvector_picksplit()
2023-09-04 14:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17950: Incorrect memory access in gtsvector_picksplit()
2023-09-05 04:58 UTC Michael Paquier <michael@paquier.xyz>
[8+ messages in thread]
UPDATE mentions the RETURNING * syntax but does not mention RETURNING * INTO ...
2023-09-04 15:55 UTC James Stuart <slim2k@privatejuris.org>
` Re: UPDATE mentions the RETURNING * syntax but does not mention RETURNING * INTO ...
2023-09-04 21:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Error on help in /src/bin/pg_basebackup/pg_basebackup.c
2023-09-01 10:34 UTC Romain MAZIÈRE <romain.maziere@sigmaz-consilium.fr>
` Re: Error on help in /src/bin/pg_basebackup/pg_basebackup.c
2023-09-01 10:50 UTC Michael Paquier <michael@paquier.xyz>
` Re: Error on help in /src/bin/pg_basebackup/pg_basebackup.c
2023-09-01 11:00 UTC Romain MAZIÈRE <romain.maziere@sigmaz-consilium.fr>
` Re: Error on help in /src/bin/pg_basebackup/pg_basebackup.c
2023-09-01 12:02 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Error on help in /src/bin/pg_basebackup/pg_basebackup.c
2023-09-01 12:13 UTC Romain MAZIÈRE <romain.maziere@sigmaz-consilium.fr>
` Re: Error on help in /src/bin/pg_basebackup/pg_basebackup.c
2023-09-01 12:25 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[6+ 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