pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #16220: FTS queries slow for large table when using low "gin_fuzzy_search_limit"
  2020-01-20 22:33 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #16219: EvalPlanQualFetchRowMark segfaults on Updates
  2020-01-20 14:54 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16219: EvalPlanQualFetchRowMark segfaults on Updates
  2020-01-20 16:14 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

Reorderbuffer crash during recovery
  2019-11-06 11:50 UTC  vignesh C <vignesh21@gmail.com>
` Re: Reorderbuffer crash during recovery
  2019-11-06 12:10 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: Reorderbuffer crash during recovery
  2019-11-07 04:25 UTC  vignesh C <vignesh21@gmail.com>
` Re: Reorderbuffer crash during recovery
  2019-11-07 05:31 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: Reorderbuffer crash during recovery
  2019-11-07 11:18 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Reorderbuffer crash during recovery
  2019-11-07 11:33 UTC  Amit Kapila <amit.kapila16@gmail.com>
` Re: Reorderbuffer crash during recovery
  2019-11-07 16:31 UTC  Andres Freund <andres@anarazel.de>
` Re: Reorderbuffer crash during recovery
  2019-11-08 04:34 UTC  vignesh C <vignesh21@gmail.com>
` Re: Reorderbuffer crash during recovery
  2019-11-09 11:37 UTC  Amit Kapila <amit.kapila16@gmail.com>
` Re: Reorderbuffer crash during recovery
  2019-11-10 11:18 UTC  vignesh C <vignesh21@gmail.com>
` Re: Reorderbuffer crash during recovery
  2019-12-11 05:43 UTC  vignesh C <vignesh21@gmail.com>
` Re: Reorderbuffer crash during recovery
  2019-12-17 09:02 UTC  Amit Kapila <amit.kapila16@gmail.com>
` Re: Reorderbuffer crash during recovery
  2019-12-27 08:20 UTC  vignesh C <vignesh21@gmail.com>
` Re: Reorderbuffer crash during recovery
  2019-12-27 15:07 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: Reorderbuffer crash during recovery
  2019-12-30 05:47 UTC  Amit Kapila <amit.kapila16@gmail.com>
` Re: Reorderbuffer crash during recovery
  2019-12-31 06:05 UTC  vignesh C <vignesh21@gmail.com>
` Re: Reorderbuffer crash during recovery
  2020-01-16 03:47 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: Reorderbuffer crash during recovery
  2020-01-17 02:12 UTC  vignesh C <vignesh21@gmail.com>
` Re: Reorderbuffer crash during recovery
  2020-01-17 03:13 UTC  Dilip Kumar <dilipbalaut@gmail.com>
` Re: Reorderbuffer crash during recovery
  2020-01-17 21:12 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: Reorderbuffer crash during recovery
  2020-01-18 05:29 UTC  Amit Kapila <amit.kapila16@gmail.com>
` Re: Reorderbuffer crash during recovery
  2020-01-20 00:36 UTC  vignesh C <vignesh21@gmail.com>
  [22+ messages in thread]

libpq parameter parsing problem
  2020-01-07 13:17 UTC  Jobin Augustine <jobinau@gmail.com>
` Re: libpq parameter parsing problem
  2020-01-07 13:27 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
` Re: libpq parameter parsing problem
  2020-01-07 14:23 UTC  Oleksandr Shulgin <oleksandr.shulgin@zalando.de>
` Re: libpq parameter parsing problem
  2020-01-08 08:48 UTC  Jobin Augustine <jobinau@gmail.com>
` Re: libpq parameter parsing problem
  2020-01-08 09:06 UTC  Heikki Linnakangas <hlinnaka@iki.fi>
` Re: libpq parameter parsing problem
  2020-01-09 04:38 UTC  Michael Paquier <michael@paquier.xyz>
` Re: libpq parameter parsing problem
  2020-01-13 14:37 UTC  Jobin Augustine <jobinau@gmail.com>
` Re: libpq parameter parsing problem
  2020-01-14 06:03 UTC  Michael Paquier <michael@paquier.xyz>
` Re: libpq parameter parsing problem
  2020-01-14 06:31 UTC  Jobin Augustine <jobinau@gmail.com>
` Re: libpq parameter parsing problem
  2020-01-14 08:55 UTC  Michael Paquier <michael@paquier.xyz>
` Re: libpq parameter parsing problem
  2020-01-14 21:56 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: libpq parameter parsing problem
  2020-01-15 01:52 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: libpq parameter parsing problem
  2020-01-15 02:40 UTC  Michael Paquier <michael@paquier.xyz>
` Re: libpq parameter parsing problem
  2020-01-15 03:54 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: libpq parameter parsing problem
  2020-01-15 05:14 UTC  Michael Paquier <michael@paquier.xyz>
` Re: libpq parameter parsing problem
  2020-01-15 15:42 UTC  Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
` Re: libpq parameter parsing problem
  2020-01-16 03:49 UTC  Michael Paquier <michael@paquier.xyz>
` Re: libpq parameter parsing problem
  2020-01-16 04:53 UTC  Jobin Augustine <jobinau@gmail.com>
` Re: libpq parameter parsing problem
  2020-01-16 08:17 UTC  Oleksandr Shulgin <oleksandr.shulgin@zalando.de>
` Re: libpq parameter parsing problem
  2020-01-17 06:29 UTC  Michael Paquier <michael@paquier.xyz>
` Re: libpq parameter parsing problem
  2020-01-17 08:05 UTC  Oleksandr Shulgin <oleksandr.shulgin@zalando.de>
` Re: libpq parameter parsing problem
  2020-01-19 10:05 UTC  Michael Paquier <michael@paquier.xyz>
  [22+ messages in thread]

BUG #16218: The database cluster initialization failed
  2020-01-18 23:15 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16218: The database cluster initialization failed
  2020-01-19 01:08 UTC  naveen goswami <rilogical@gmail.com>
  [2+ messages in thread]

BUG #16193: Tools menu in pgAdmin is not shown
  2020-01-06 14:58 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16193: Tools menu in pgAdmin is not shown
  2020-01-18 17:49 UTC  Bruce Momjian <bruce@momjian.us>
  [2+ messages in thread]

BUG #16208: background worker "logical replication worker" was terminated by signal 11: Segmentation
  2020-01-16 12:26 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16208: background worker "logical replication worker" was terminated by signal 11: Segmentation
  2020-01-17 00:12 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16208: background worker "logical replication worker" was terminated by signal 11: Segmentation
  2020-01-18 08:17 UTC  Mr Kaleek <mr.kaleek@gmail.com>
` Re: BUG #16208: background worker "logical replication worker" was terminated by signal 11: Segmentation
  2020-01-18 10:44 UTC  Michael Paquier <michael@paquier.xyz>
  [4+ messages in thread]

Bug on pldebugger
  2020-01-18 02:40 UTC  陈佳昕(步真) <buzhen.cjx@alibaba-inc.com>

BUG #16213: segfault when running a query
  2020-01-16 23:27 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16213: segfault when running a query
  2020-01-17 04:03 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16213: segfault when running a query
  2020-01-17 18:29 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

BUG #16216: the result of to_date function with negative year number not same as BC year number
  2020-01-17 12:42 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16216: the result of to_date function with negative year number not same as BC year number
  2020-01-17 14:17 UTC  Fabien COELHO <coelho@cri.ensmp.fr>
` Re: BUG #16216: the result of to_date function with negative year number not same as BC year number
  2020-01-17 14:59 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16216: the result of to_date function with negative year number not same as BC year number
  2020-01-17 15:15 UTC  Fabien COELHO <coelho@cri.ensmp.fr>
` Re: BUG #16216: the result of to_date function with negative year number not same as BC year number
  2020-01-17 15:29 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [5+ messages in thread]

BUG #16217: ECPG call interface && filename of the foo.pgc file for logging
  2020-01-17 15:03 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #16215: Restore failes if number of workers in postgresql.conf is lower than on source system
  2020-01-17 07:22 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16215: Restore failes if number of workers in postgresql.conf is lower than on source system
  2020-01-17 07:58 UTC  Sergei Kornilov <sk@zsrv.org>
` Re: BUG #16215: Restore failes if number of workers in postgresql.conf is lower than on source system
  2020-01-17 09:33 UTC  Stefan Sonnenberg-Carstens <stefan.sonnenberg.carstens@gmail.com>
` Re: BUG #16215: Restore failes if number of workers in postgresql.conf is lower than on source system
  2020-01-17 09:45 UTC  Sergei Kornilov <sk@zsrv.org>
` Re: BUG #16215: Restore failes if number of workers in postgresql.conf is lower than on source system
  2020-01-17 10:42 UTC  Stefan Sonnenberg-Carstens <stefan.sonnenberg.carstens@gmail.com>
  [5+ messages in thread]

BUG #16214: Settings is not copy
  2020-01-17 04:23 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16214: Settings is not copy
  2020-01-17 05:37 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #16212: subquery block allows to overwrite table alias defined earlier
  2020-01-16 22:36 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16212: subquery block allows to overwrite table alias defined earlier
  2020-01-17 00:11 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16212: subquery block allows to overwrite table alias defined earlier
  2020-01-17 00:16 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [3+ messages in thread]

BUG #16205: background worker "logical replication worker" (PID 25218) was terminated by signal 11: Segmentation
  2020-01-15 02:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16205: background worker "logical replication worker" (PID 25218) was terminated by signal 11: Segmentation
  2020-01-15 02:58 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16205: background worker "logical replication worker" (PID 25218) was terminated by signal 11: Segmentation
  2020-01-15 04:02 UTC  Pendekar Dikala Senja <pendekar.senja@outlook.com>
` Re: BUG #16205: background worker "logical replication worker" (PID 25218) was terminated by signal 11: Segmentation
  2020-01-15 04:42 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16205: background worker "logical replication worker" (PID 25218) was terminated by signal 11: Segmentation
  2020-01-15 10:02 UTC  Mahendra Singh Thalor <mahi6run@gmail.com>
` Re: BUG #16205: background worker "logical replication worker" (PID 25218) was terminated by signal 11: Segmentation
  2020-01-15 10:08 UTC  Pendekar Dikala Senja <pendekar.senja@outlook.com>
` Re: BUG #16205: background worker "logical replication worker" (PID 25218) was terminated by signal 11: Segmentation
  2020-01-16 03:20 UTC  Pendekar Dikala Senja <pendekar.senja@outlook.com>
` Re: BUG #16205: background worker "logical replication worker" (PID 25218) was terminated by signal 11: Segmentation
  2020-01-16 03:30 UTC  Mahendra Singh Thalor <mahi6run@gmail.com>
` Re: BUG #16205: background worker "logical replication worker" (PID 25218) was terminated by signal 11: Segmentation
  2020-01-16 03:44 UTC  Pendekar Dikala Senja <pendekar.senja@outlook.com>
` Re: BUG #16205: background worker "logical replication worker" (PID 25218) was terminated by signal 11: Segmentation
  2020-01-16 03:47 UTC  Pendekar Dikala Senja <pendekar.senja@outlook.com>
` Re: BUG #16205: background worker "logical replication worker" (PID 25218) was terminated by signal 11: Segmentation
  2020-01-16 18:46 UTC  Christophe Pettus <xof@thebuild.com>
` Re: BUG #16205: background worker "logical replication worker" (PID 25218) was terminated by signal 11: Segmentation
  2020-01-16 23:45 UTC  Michael Paquier <michael@paquier.xyz>
  [12+ messages in thread]

BUG #16210: Space
  2020-01-16 16:40 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16210: Space
  2020-01-16 16:49 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [2+ messages in thread]

BUG #16211: Disk space keep rising for originated tablespace of base Database
  2020-01-16 16:47 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #16209: cant install via https://www.postgresql.org/download/linux/redhat/
  2020-01-16 13:07 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #16207: localization functions upper() and lower() does not work for text returned by convert_from()
  2020-01-15 15:41 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16207: localization functions upper() and lower() does not work for text returned by convert_from()
  2020-01-15 16:30 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

create rule with multiple commands
  2020-01-15 09:46 UTC  andreas@elbrief.de
` Re: create rule with multiple commands
  2020-01-15 15:40 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #16206: Documentation for PGDATABASE libpq env var is misleading
  2020-01-15 08:35 UTC  PG Bug reporting form <noreply@postgresql.org>

Oracle To Community Postgresql Migration
  2020-01-14 07:52 UTC  Vijay Ingle <vjingle143@gmail.com>
` Re: Oracle To Community Postgresql Migration
  2020-01-14 07:57 UTC  Julien Rouhaud <rjuju123@gmail.com>
` Re: Oracle To Community Postgresql Migration
  2020-01-14 12:54 UTC  Vijay Ingle <vjingle143@gmail.com>
` Re: Oracle To Community Postgresql Migration
  2020-01-14 13:13 UTC  Pavel Stehule <pavel.stehule@gmail.com>
  [4+ messages in thread]

Unable to create a server
  2020-01-12 17:11 UTC  Lee Everest <ab5sr@hotmail.com>
` Re: Unable to create a server
  2020-01-13 04:23 UTC  Fahar Abbas <fahar.abbas@enterprisedb.com>
` Re: Unable to create a server
  2020-01-14 12:22 UTC  Fahar Abbas <fahar.abbas@enterprisedb.com>
  [3+ messages in thread]

BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2019-11-18 01:27 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2019-11-18 04:50 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2019-11-18 12:03 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2019-11-18 22:51 UTC  Adam Scott <adam.c.scott@gmail.com>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2019-11-18 23:59 UTC  Adam Scott <adam.c.scott@gmail.com>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2019-11-19 00:57 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2019-11-19 01:48 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2019-11-19 02:22 UTC  Adam Scott <adam.c.scott@gmail.com>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2019-11-19 03:04 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2019-11-19 10:18 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2019-11-19 10:38 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2019-11-19 11:40 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2019-12-10 03:43 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2019-12-10 05:38 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2020-01-03 19:05 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2020-01-04 17:57 UTC  Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2020-01-06 20:28 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2020-01-07 06:39 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2020-01-07 15:08 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2020-01-09 05:45 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2020-01-12 19:39 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2020-01-13 18:56 UTC  Adam Scott <adam.c.scott@gmail.com>
` Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
  2020-01-13 22:33 UTC  Michael Paquier <michael@paquier.xyz>
  [23+ messages in thread]

Cannot create index on Jsonb timestamp field
  2020-01-13 14:41 UTC  Raschkowski, Michael <michael.raschkowski@auconet-it.com>
` Re: Cannot create index on Jsonb timestamp field
  2020-01-13 15:56 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` Re: Cannot create index on Jsonb timestamp field
  2020-01-13 16:26 UTC  Pavel Stehule <pavel.stehule@gmail.com>
  [3+ 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