pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedDROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-01-13 15:23 UTC Lakshmi Narayanan Sreethar <lakshmi@timescale.com>
` Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-01-14 16:02 UTC Andres Freund <andres@anarazel.de>
` Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-01-14 17:20 UTC Andres Freund <andres@anarazel.de>
` Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-01-16 09:32 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-01-17 00:53 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-01-17 10:56 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-01-17 20:04 UTC Andres Freund <andres@anarazel.de>
` Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-01-18 04:32 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-01-19 07:14 UTC houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
` RE: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-01-19 10:16 UTC houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
` Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-01-19 11:07 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-01-20 05:24 UTC vignesh C <vignesh21@gmail.com>
` Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-01-21 11:36 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-01-24 05:35 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-01-24 05:40 UTC Andres Freund <andres@anarazel.de>
` Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-08-01 13:15 UTC Andrey M. Borodin <x4mmm@yandex-team.ru>
` Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-08-02 05:20 UTC Amit Kapila <amit.kapila16@gmail.com>
` RE: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-08-02 06:12 UTC Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com>
` Re: DROP DATABASE deadlocks with logical replication worker in PG 15.1
2023-08-02 08:34 UTC Andrey M. Borodin <x4mmm@yandex-team.ru>
[19+ messages in thread]
BUG #18035: Assertion failure in jsonb_path_query
2023-07-25 08:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18035: Assertion failure in jsonb_path_query
2023-07-25 14:55 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18035: Assertion failure in jsonb_path_query
2023-08-01 13:46 UTC David Rowley <dgrowleyml@gmail.com>
[3+ messages in thread]
(record = record) inconsistent with record_eq(arg1, arg2)
2023-07-31 13:45 UTC jian he <jian.universality@gmail.com>
` (record = record) inconsistent with record_eq(arg1, arg2)
2023-07-31 14:52 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: (record = record) inconsistent with record_eq(arg1, arg2)
2023-07-31 20:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #18043: Merge fails to insert when source and target are same table and table is empty (contains no rows)
2023-07-30 16:17 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18042: Query planner favor index corresponding to a order by with a limit even when there is a where
2023-07-28 18:40 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18042: Query planner favor index corresponding to a order by with a limit even when there is a where
2023-07-28 19:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18042: Query planner favor index corresponding to a order by with a limit even when there is a where
2023-07-28 21:02 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: BUG #18042: Query planner favor index corresponding to a order by with a limit even when there is a where
2023-07-29 14:45 UTC Christian Vallières <christian.vallieres@evimbec.ca>
[4+ messages in thread]
Question about double table scans for a table
2023-07-27 08:17 UTC Ba Jinsheng <bajinsheng@u.nus.edu>
` Re: Question about double table scans for a table
2023-07-27 20:38 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Question about double table scans for a table
2023-07-28 00:11 UTC jian he <jian.universality@gmail.com>
` Re: Question about double table scans for a table
2023-07-28 04:01 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Question about double table scans for a table
2023-07-28 05:34 UTC jian he <jian.universality@gmail.com>
` Re: Question about double table scans for a table
2023-07-28 13:26 UTC Jeff Janes <jeff.janes@gmail.com>
[6+ messages in thread]
BUG #18038: Aliases removed from view definitions
2023-07-27 06:29 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18038: Aliases removed from view definitions
2023-07-27 14:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18038: Aliases removed from view definitions
2023-07-28 05:33 UTC Asier Lostalé <asier.lostale@openbravo.com>
` Re: BUG #18038: Aliases removed from view definitions
2023-07-28 05:45 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18038: Aliases removed from view definitions
2023-07-28 06:22 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[5+ messages in thread]
Documentation bug at: current/sql-vacuum.html, Notes
2023-07-26 17:39 UTC Christophe Pettus <xof@thebuild.com>
` Re: Documentation bug at: current/sql-vacuum.html, Notes
2023-07-26 17:55 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Documentation bug at: current/sql-vacuum.html, Notes
2023-07-26 18:12 UTC Christophe Pettus <xof@thebuild.com>
[3+ messages in thread]
BUG #18036: Query planner chooses sub-optimal query path given enough IN tuples.
2023-07-26 04:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18036: Query planner chooses sub-optimal query path given enough IN tuples.
2023-07-26 11:08 UTC Magnus Hagander <magnus@hagander.net>
[2+ messages in thread]
BUG #18031: Segmentation fault after deadlock within VACUUM's parallel worker
2023-07-19 15:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18031: Segmentation fault after deadlock within VACUUM's parallel worker
2023-07-21 08:01 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18031: Segmentation fault after deadlock within VACUUM's parallel worker
2023-07-22 10:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18031: Segmentation fault after deadlock within VACUUM's parallel worker
2023-07-24 01:39 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18031: Segmentation fault after deadlock within VACUUM's parallel worker
2023-07-25 03:39 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #18031: Segmentation fault after deadlock within VACUUM's parallel worker
2023-07-25 07:35 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #18031: Segmentation fault after deadlock within VACUUM's parallel worker
2023-07-25 16:27 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #18031: Segmentation fault after deadlock within VACUUM's parallel worker
2023-07-26 05:55 UTC Masahiko Sawada <sawada.mshk@gmail.com>
[8+ messages in thread]
Add instructions for downloading Linux (Mint)
2023-07-25 09:30 UTC Черников Д А <DAChernikov@niiar.ru>
BUG #18018: Homebrew link is broken
2023-07-10 22:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18018: Homebrew link is broken
2023-07-11 18:14 UTC Gurjeet Singh <gurjeet@singh.im>
` Re: BUG #18018: Homebrew link is broken
2023-07-11 23:39 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18018: Homebrew link is broken
2023-07-12 12:49 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18018: Homebrew link is broken
2023-07-12 13:45 UTC Jonathan S. Katz <jkatz@postgresql.org>
` Re: BUG #18018: Homebrew link is broken
2023-07-12 13:59 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18018: Homebrew link is broken
2023-07-25 02:17 UTC Jonathan S. Katz <jkatz@postgresql.org>
[7+ messages in thread]
BUG #18027: Logical replication taking forever
2023-07-17 22:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18027: Logical replication taking forever
2023-07-19 04:19 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18027: Logical replication taking forever
2023-07-19 04:59 UTC Andres Martin del Campo Campos <andres@invisible.email>
` Re: BUG #18027: Logical replication taking forever
2023-07-19 11:07 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #18027: Logical replication taking forever
2023-07-20 17:16 UTC Andres Martin del Campo Campos <andres@invisible.email>
` Re: BUG #18027: Logical replication taking forever
2023-07-21 08:56 UTC vignesh C <vignesh21@gmail.com>
` Re: BUG #18027: Logical replication taking forever
2023-07-22 05:25 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18027: Logical replication taking forever
2023-07-24 18:03 UTC Andres Martin del Campo Campos <andres@invisible.email>
[8+ messages in thread]
BUG #18033: org.postgresql.util.PSQLException:
2023-07-20 03:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18033: org.postgresql.util.PSQLException:
2023-07-20 08:47 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18033: org.postgresql.util.PSQLException:
2023-07-20 14:58 UTC Shashanth Reddy <shashanthreddy7@gmail.com>
` Re: BUG #18033: org.postgresql.util.PSQLException:
2023-07-20 15:06 UTC Daniel Gustafsson <daniel@yesql.se>
[4+ messages in thread]
BUG #18030: Large memory consumption caused by in-clause subqueries
2023-07-19 08:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18030: Large memory consumption caused by in-clause subqueries
2023-07-19 10:39 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18030: Large memory consumption caused by in-clause subqueries
2023-07-19 23:13 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18030: Large memory consumption caused by in-clause subqueries
2023-07-20 00:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #18019: misbehaviour by replication
2023-07-12 10:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18019: misbehaviour by replication
2023-07-13 07:49 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` RE: BUG #18019: misbehaviour by replication
2023-07-13 08:21 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #18019: misbehaviour by replication
2023-07-13 09:03 UTC André Kutepow <a.kutepow@prodat-sql.de>
` Re: BUG #18019: misbehaviour by replication
2023-07-13 10:28 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18019: misbehaviour by replication
2023-07-13 10:30 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18019: misbehaviour by replication
2023-07-19 06:52 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
[7+ messages in thread]
BUG #18029: Misleading warning about Collation Changes with newer glibc version
2023-07-19 06:32 UTC PG Bug reporting form <noreply@postgresql.org>
Bug with aggregate Window Functions when using Order By. Elements dropped if order by provided
2023-07-17 21:41 UTC Walker Philips <walker.philips@oakworth.com>
` Re: Bug with aggregate Window Functions when using Order By. Elements dropped if order by provided
2023-07-18 10:10 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Bug with aggregate Window Functions when using Order By. Elements dropped if order by provided
2023-07-18 11:14 UTC David Rowley <dgrowleyml@gmail.com>
[3+ messages in thread]
pg_dump needs an option to add the force flag to the drop database
2023-07-17 08:47 UTC Joan <aseques@gmail.com>
` Re: pg_dump needs an option to add the force flag to the drop database
2023-07-18 03:40 UTC vignesh C <vignesh21@gmail.com>
` Re: pg_dump needs an option to add the force flag to the drop database
2023-07-18 03:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump needs an option to add the force flag to the drop database
2023-07-18 07:48 UTC Joan <aseques@gmail.com>
[4+ messages in thread]
BUG #18026: compile error / fe-auth.c:807:64: error: 'CHAR_BIT' undeclared (first use in this function)
2023-07-17 15:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18026: compile error / fe-auth.c:807:64: error: 'CHAR_BIT' undeclared (first use in this function)
2023-07-17 16:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18026: compile error / fe-auth.c:807:64: error: 'CHAR_BIT' undeclared (first use in this function)
2023-07-17 16:21 UTC Marcel Hofstetter <hofstetter@jomasoft.ch>
` Re: BUG #18026: compile error / fe-auth.c:807:64: error: 'CHAR_BIT' undeclared (first use in this function)
2023-07-17 18:46 UTC Marcel Hofstetter <hofstetter@jomasoft.ch>
` Re: BUG #18026: compile error / fe-auth.c:807:64: error: 'CHAR_BIT' undeclared (first use in this function)
2023-07-17 18:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18026: compile error / fe-auth.c:807:64: error: 'CHAR_BIT' undeclared (first use in this function)
2023-07-17 20:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18026: compile error / fe-auth.c:807:64: error: 'CHAR_BIT' undeclared (first use in this function)
2023-07-18 05:44 UTC Michael Paquier <michael@paquier.xyz>
[7+ messages in thread]
Query returns error "there is no parameter $1" but server logs that there are two parameters supplied
2023-07-17 02:25 UTC Paul De Audney <paul.deaudney@safetyculture.io>
` Re: Query returns error "there is no parameter $1" but server logs that there are two parameters supplied
2023-07-17 07:58 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Query returns error "there is no parameter $1" but server logs that there are two parameters supplied
2023-07-17 13:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query returns error "there is no parameter $1" but server logs that there are two parameters supplied
2023-07-17 23:27 UTC Paul De Audney <paul.deaudney@safetyculture.io>
[4+ messages in thread]
BUG #18025: Probably we need to change behaviour of the checkpoint failures in PG
2023-07-17 05:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18025: Probably we need to change behaviour of the checkpoint failures in PG
2023-07-17 07:53 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18025: Probably we need to change behaviour of the checkpoint failures in PG
2023-07-17 08:06 UTC Michael Paquier <michael@paquier.xyz>
[3+ messages in thread]
BUG #18021: Loading Error
2023-07-15 08:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18021: Loading Error
2023-07-17 07:37 UTC Manika Singhal <manika.singhal@enterprisedb.com>
[2+ messages in thread]
BUG #18023: when the query shows an error SQL Error [XX000]: ERROR: pg_attribute catalog is missing
2023-07-16 09:27 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18012: Installer fails to run .bat files when they are registered to Notepad++
2023-07-02 06:42 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18012: Installer fails to run .bat files when they are registered to Notepad++
2023-07-04 10:54 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` Re: BUG #18012: Installer fails to run .bat files when they are registered to Notepad++
2023-07-13 13:05 UTC Manika Singhal <manika.singhal@enterprisedb.com>
` Re: BUG #18012: Installer fails to run .bat files when they are registered to Notepad++
2023-07-14 05:08 UTC Matt Feemster <matt.feemster@gmail.com>
[4+ 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