pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #18053: fastpath count per pid in pg_locks shows > 16 entries
  2023-08-10 12:31 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 08:55 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 12:57 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 14:04 UTC  Nicolas Gouteux <nicolas.gouteux@sonarsource.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 14:28 UTC  Nicolas Gouteux <nicolas.gouteux@sonarsource.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 14:37 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 14:43 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 14:47 UTC  Nicolas Gouteux <nicolas.gouteux@sonarsource.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 14:49 UTC  Nicolas Gouteux <nicolas.gouteux@sonarsource.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 15:02 UTC  Félix GERZAGUET <felix.gerzaguet@gmail.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 15:03 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18051: char(N) and varchar(N) behave opposite to the documentation
  2023-08-09 15:26 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [11+ messages in thread]

BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-25 12:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-25 14:40 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-26 06:49 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-26 08:05 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-27 11:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-28 06:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-28 07:02 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-29 02:22 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-29 09:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-29 10:39 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-30 04:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-06-30 05:59 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-08-02 18:01 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index
  2023-08-08 00:31 UTC  Michael Paquier <michael@paquier.xyz>
  [14+ messages in thread]

search_path not recomputed when role name changes
  2023-07-27 18:21 UTC  Jeff Davis <pgsql@j-davis.com>
` Re: search_path not recomputed when role name changes
  2023-07-30 04:08 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: search_path not recomputed when role name changes
  2023-07-30 05:58 UTC  Michael Paquier <michael@paquier.xyz>
` Re: search_path not recomputed when role name changes
  2023-08-02 19:09 UTC  Jeff Davis <pgsql@j-davis.com>
` Re: search_path not recomputed when role name changes
  2023-08-03 23:28 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: search_path not recomputed when role name changes
  2023-08-07 23:20 UTC  Michael Paquier <michael@paquier.xyz>
  [6+ messages in thread]

BUG #18049: dynamic_shared_memory_type's value `posix` doesn't have any effect, syscall shm_get executes
  2023-08-04 05:22 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18049: dynamic_shared_memory_type's value `posix` doesn't have any effect, syscall shm_get executes
  2023-08-04 13:22 UTC  Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #18049: dynamic_shared_memory_type's value `posix` doesn't have any effect, syscall shm_get executes
  2023-08-07 14:38 UTC  jitu <jkr0103@gmail.com>
  [3+ messages in thread]

PostgreSQL doesn't display exact version
  2023-08-06 16:19 UTC  Jacob Pfundstein <jjpfst@gmail.com>

AW: WHERE column = X AND column = Y will always be zero matching rows
  2023-08-03 14:53 UTC  [Quipsy] Markus Karg <karg@quipsy.de>
` AW: WHERE column = X AND column = Y will always be zero matching rows
  2023-08-04 06:12 UTC  [Quipsy] Markus Karg <karg@quipsy.de>
  [2+ messages in thread]

BUG #18047: ODBC to PG long transaction causes PANIC
  2023-08-03 01:28 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18047: ODBC to PG long transaction causes PANIC
  2023-08-03 05:08 UTC  justin tocci <justin@tocci.org>
` Re: BUG #18047: ODBC to PG long transaction causes PANIC
  2023-08-03 05:14 UTC  Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #18047: ODBC to PG long transaction causes PANIC
  2023-08-03 14:48 UTC  Justin Tocci <justin@wfprod.com>
` Re: BUG #18047: ODBC to PG long transaction causes PANIC
  2023-08-03 23:31 UTC  Thomas Munro <thomas.munro@gmail.com>
  [5+ messages in thread]

WHERE column = X AND column = Y will always be zero matching rows
  2023-08-03 14:20 UTC  [Quipsy] Markus Karg <karg@quipsy.de>
` Re: WHERE column = X AND column = Y will always be zero matching rows
  2023-08-03 14:48 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: WHERE column = X AND column = Y will always be zero matching rows
  2023-08-03 14:53 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: WHERE column = X AND column = Y will always be zero matching rows
  2023-08-03 15:02 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: WHERE column = X AND column = Y will always be zero matching rows
  2023-08-03 17:55 UTC  Jaime Casanova <jcasanov@systemguards.com.ec>
` Re: WHERE column = X AND column = Y will always be zero matching rows
  2023-08-03 17:59 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [6+ messages in thread]

BUG #18048: Database process terminated automatically
  2023-08-03 10:27 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18048: Database process terminated automatically
  2023-08-03 11:42 UTC  David Rowley <dgrowleyml@gmail.com>
  [2+ messages in thread]

[BUG REPORT] Unexpected cast while matching CHAR type
  2023-08-02 17:23 UTC  翁思扬 <52275903002@stu.ecnu.edu.cn>
` Re: [BUG REPORT] Unexpected cast while matching CHAR type
  2023-08-02 18:35 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #18045: NpgSQL installation not working
  2023-08-01 14:37 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18045: NpgSQL installation not working
  2023-08-02 16:29 UTC  Euler Taveira <euler@eulerto.com>
  [2+ messages in thread]

pg_hba.conf "authentication file token too long, skipping"
  2023-07-24 15:05 UTC  Zechman, Derek S <Derek.S.Zechman@snapon.com>
` Re: pg_hba.conf "authentication file token too long, skipping"
  2023-07-24 16:51 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` RE: pg_hba.conf "authentication file token too long, skipping"
  2023-08-01 16:29 UTC  Zechman, Derek S <Derek.S.Zechman@snapon.com>
` Re: pg_hba.conf "authentication file token too long, skipping"
  2023-08-02 16:20 UTC  Euler Taveira <euler@eulerto.com>
  [4+ messages in thread]

DROP 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]


[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