pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #16578: When making an insert, the database goes to recover mode
  2020-08-12 07:45 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16578: When making an insert, the database goes to recover mode
  2020-08-12 12:41 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

AW: AW: posgres 12 bug (partitioned table)
  2020-08-12 10:57 UTC  Wilm Hoyer <W.Hoyer@dental-vision.de>
` Re: AW: AW: posgres 12 bug (partitioned table)
  2020-08-12 11:08 UTC  Pavel Biryukov <79166341370@yandex.ru>
  [2+ messages in thread]

Re: [noreply@postgresql.org: BUG #16575: Linux Mint 20, ulyana won't update postgres as described]
  2020-08-11 09:05 UTC  Christoph Berg <myon@debian.org>

BUG #16573: pgbouncer 1.14 addition to EL6 breaks installation
  2020-08-04 18:21 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16573: pgbouncer 1.14 addition to EL6 breaks installation
  2020-08-10 23:54 UTC  Devrim Gündüz <devrim@gunduz.org>
  [2+ messages in thread]

BUG #16576: Creating a connection using psycopg2 results in "zombie" ccapiserver.exe processes on Windows
  2020-08-07 15:52 UTC  PG Bug reporting form <noreply@postgresql.org>

Re: BUG #16556: The database cluster initialisation failed - Win 10 postgresql 12.3 version installation error
  2020-08-04 17:28 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: BUG #16556: The database cluster initialisation failed - Win 10 postgresql 12.3 version installation error
  2020-08-07 04:28 UTC  Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
  [2+ messages in thread]

BUG #16575: Linux Mint 20, ulyana won't update postgres as described
  2020-08-07 03:57 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #16570: Collation not working
  2020-08-03 07:14 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16570: Collation not working
  2020-08-03 17:35 UTC  Daniel Verite <daniel@manitou-mail.org>
` Re: BUG #16570: Collation not working
  2020-08-04 07:15 UTC  Arnaud Perrier <arnaud.perrier@gmail.com>
` Re: BUG #16570: Collation not working
  2020-08-04 14:32 UTC  Daniel Verite <daniel@manitou-mail.org>
` Re: BUG #16570: Collation not working
  2020-08-04 22:36 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16570: Collation not working
  2020-08-05 06:41 UTC  Arnaud Perrier <arnaud.perrier@gmail.com>
` Re: BUG #16570: Collation not working
  2020-08-05 14:49 UTC  Daniel Verite <daniel@manitou-mail.org>
` Re: BUG #16570: Collation not working
  2020-08-05 20:31 UTC  Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
` Re: BUG #16570: Collation not working
  2020-08-05 21:30 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16570: Collation not working
  2020-08-06 21:18 UTC  Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
  [10+ messages in thread]

Index not used without explicit typecast
  2020-08-05 13:05 UTC  Jan Kort <jan.kort@genetics.nl>
` Re: Index not used without explicit typecast
  2020-08-05 14:32 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Index not used without explicit typecast
  2020-08-05 16:39 UTC  Jan Kort <jan.kort@genetics.nl>
` Re: Index not used without explicit typecast
  2020-08-06 03:48 UTC  Pavel Stehule <pavel.stehule@gmail.com>
  [4+ messages in thread]

BUG #16574: Error in configuration of pgadmin4-server (amd64 4.24) on Debian version 10.5
  2020-08-05 11:46 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #16572: pgadmin change column order
  2020-08-04 14:18 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16572: pgadmin change column order
  2020-08-04 15:08 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #16572: pgadmin change column order
  2020-08-05 08:10 UTC  Guillaume Lelarge <guillaume@lelarge.info>
  [3+ messages in thread]

BUG #16569: Document "59.2. Built-in Operator Classes" have a clerical error
  2020-08-03 03:28 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16569: Document "59.2. Built-in Operator Classes" have a clerical error
  2020-08-04 17:11 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
  [2+ messages in thread]

BUG #16571: "time with time zone" type can input '00:00:00+1559'::time with time zone
  2020-08-03 07:26 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16571: "time with time zone" type can input '00:00:00+1559'::time with time zone
  2020-08-03 14:18 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #16568: pg_upgrade failed from 9.3 to 9.6
  2020-08-01 08:27 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16568: pg_upgrade failed from 9.3 to 9.6
  2020-08-02 21:11 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #16566: Consistently link latest repo RPM release to pgdg-redhat-repo-latest (ref #16074)
  2020-07-31 19:09 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16566: Consistently link latest repo RPM release to pgdg-redhat-repo-latest (ref #16074)
  2020-07-31 20:00 UTC  Devrim Gündüz <devrim@gunduz.org>
` Re: BUG #16566: Consistently link latest repo RPM release to pgdg-redhat-repo-latest (ref #16074)
  2020-07-31 20:33 UTC  Matt Saladna <matt@apisnetworks.com>
  [3+ messages in thread]

Backend stuck in tirigger.c:afterTriggerInvokeEvents forever
  2020-04-21 04:07 UTC  cbw <cbwhitebu@gmail.com>
` Re: Backend stuck in tirigger.c:afterTriggerInvokeEvents forever
  2020-04-21 14:44 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Backend stuck in tirigger.c:afterTriggerInvokeEvents forever
  2020-04-21 15:13 UTC  cbw <cbwhitebu@gmail.com>
` Re: Backend stuck in tirigger.c:afterTriggerInvokeEvents forever
  2020-04-21 15:19 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: Backend stuck in tirigger.c:afterTriggerInvokeEvents forever
  2020-04-21 15:37 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Backend stuck in tirigger.c:afterTriggerInvokeEvents forever
  2020-04-23 03:39 UTC  Andres Freund <andres@anarazel.de>
` Re: Backend stuck in tirigger.c:afterTriggerInvokeEvents forever
  2020-04-24 16:35 UTC  cbw <cbwhitebu@gmail.com>
` Re: Backend stuck in tirigger.c:afterTriggerInvokeEvents forever
  2020-07-31 19:51 UTC  cbw <cbwhitebu@gmail.com>
  [8+ messages in thread]

Re: BUG #16558: `AND FALSE` increases planning time of query on 2 tables with 1000 partitions to more than 7 seconds
  2020-07-31 01:13 UTC  Tom Lane <tgl@sss.pgh.pa.us>

BUG #16500: SQL Abend. select multi_key_columns_range_partition_table
  2020-06-18 09:35 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table
  2020-06-18 13:05 UTC  Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table
  2020-06-18 16:44 UTC  Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table
  2020-07-01 12:55 UTC  Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table
  2020-07-02 11:52 UTC  Etsuro Fujita <etsuro.fujita@gmail.com>
  [5+ messages in thread]

BUG #15615: pg_upgrade and vacuum_defer_cleanup_age
  2019-01-31 16:19 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #15615: pg_upgrade and vacuum_defer_cleanup_age
  2020-07-02 09:33 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
  [2+ messages in thread]

BUG #16523: The wal logs fill the disk and are not cleaned up
  2020-07-02 03:16 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #16521: n_distinct_inherited does not affect child partitions when set on main partition
  2020-06-30 20:02 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16521: n_distinct_inherited does not affect child partitions when set on main partition
  2020-06-30 22:56 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #16521: n_distinct_inherited does not affect child partitions when set on main partition
  2020-07-01 17:16 UTC  Klaudie Willis <Klaudie.Willis@protonmail.com>
  [3+ messages in thread]

[bug] Table not have typarray when created by single user mode
  2020-04-13 08:25 UTC  wenjing <wjzeng2012@gmail.com>
` Re: [bug] Table not have typarray when created by single user mode
  2020-04-13 14:51 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: [bug] Table not have typarray when created by single user mode
  2020-04-14 03:16 UTC  wenjing <wjzeng2012@gmail.com>
` Re: [bug] Table not have typarray when created by single user mode
  2020-04-14 18:00 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: [bug] Table not have typarray when created by single user mode
  2020-05-19 08:19 UTC  wenjing zeng <wjzeng2012@gmail.com>
` Re: [bug] Table not have typarray when created by single user mode
  2020-05-19 09:40 UTC  shawn wang <shawn.wang.pg@gmail.com>
` Re: [bug] Table not have typarray when created by single user mode
  2020-05-19 15:32 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: [bug] Table not have typarray when created by single user mode
  2020-05-19 16:09 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: [bug] Table not have typarray when created by single user mode
  2020-05-20 08:15 UTC  shawn wang <shawn.wang.pg@gmail.com>
` Re: [bug] Table not have typarray when created by single user mode
  2020-05-21 07:28 UTC  wenjing zeng <wjzeng2012@gmail.com>
` Re: [bug] Table not have typarray when created by single user mode
  2020-05-21 08:10 UTC  Shawn Wang <shawn.wang.pg@gmail.com>
` Re: [bug] Table not have typarray when created by single user mode
  2020-05-21 11:37 UTC  Amit Kapila <amit.kapila16@gmail.com>
` Re: [bug] Table not have typarray when created by single user mode
  2020-05-25 03:37 UTC  shawn wang <shawn.wang.pg@gmail.com>
` Re: [bug] Table not have typarray when created by single user mode
  2020-07-01 16:47 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [14+ messages in thread]

BUG #16522: No anti-violent cracking mechanism
  2020-07-01 10:01 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16522: No anti-violent cracking mechanism
  2020-07-01 10:54 UTC  Magnus Hagander <magnus@hagander.net>
  [2+ messages in thread]

BUG #16516: when testing jit get terminate called after throwing an instance of 'std::bad_function_call'
  2020-06-29 09:13 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16516: when testing jit get terminate called after throwing an instance of 'std::bad_function_call'
  2020-06-30 04:28 UTC  Hamid Akhtar <hamid.akhtar@gmail.com>
` Re: BUG #16516: when testing jit get terminate called after throwing an instance of 'std::bad_function_call'
  2020-06-30 04:35 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #16516: when testing jit get terminate called after throwing an instance of 'std::bad_function_call'
  2020-07-01 07:25 UTC  Reiner Peterke <reiner.peterke@splendiddata.com>
  [4+ messages in thread]

[BUG][PATCH] ecpg crash with bytea type and cursors
  2020-06-30 13:30 UTC  Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
` Re: [BUG][PATCH] ecpg crash with bytea type and cursors
  2020-06-30 16:38 UTC  Michael Meskes <meskes@postgresql.org>
` Re: [BUG][PATCH] ecpg crash with bytea type and cursors
  2020-06-30 16:57 UTC  Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
` Re: [BUG][PATCH] ecpg crash with bytea type and cursors
  2020-06-30 17:18 UTC  Michael Meskes <meskes@postgresql.org>
` Re: [BUG][PATCH] ecpg crash with bytea type and cursors
  2020-06-30 17:19 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: [BUG][PATCH] ecpg crash with bytea type and cursors
  2020-06-30 18:15 UTC  Michael Meskes <meskes@postgresql.org>
` Re: [BUG][PATCH] ecpg crash with bytea type and cursors
  2020-06-30 18:47 UTC  Michael Meskes <meskes@postgresql.org>
` Re: [BUG][PATCH] ecpg crash with bytea type and cursors
  2020-06-30 19:47 UTC  Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
  [8+ 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