pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
EXPLAIN ANALYZE not displaying recheck condition
  2019-11-07 22:04 UTC  Ryan Lambert <ryan@rustprooflabs.com>
` Re: EXPLAIN ANALYZE not displaying recheck condition
  2019-11-08 15:47 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: EXPLAIN ANALYZE not displaying recheck condition
  2019-11-08 18:54 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: EXPLAIN ANALYZE not displaying recheck condition
  2019-11-09 14:49 UTC  Ryan Lambert <ryan@rustprooflabs.com>
  [4+ messages in thread]

BUG #16105: trying to install pgadmin4
  2019-11-09 09:46 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16105: trying to install pgadmin4
  2019-11-09 10:01 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
  [2+ messages in thread]

BUG #16100: Cannot access to the sever with the password
  2019-11-07 18:03 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16100: Cannot access to the sever with the password
  2019-11-07 21:26 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: BUG #16100: Cannot access to the sever with the password
  2019-11-08 11:24 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
  [3+ messages in thread]

pg_dump: error: schema with OID 7956828 does not exist
  2019-11-08 06:59 UTC  nemo <dbyzaa@163.com>
` Re: pg_dump: error: schema with OID 7956828 does not exist
  2019-11-08 11:18 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
  [2+ messages in thread]

BUG #16099: Segmentation fault with - triggers and procedures
  2019-11-07 15:47 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16099: Segmentation fault with - triggers and procedures
  2019-11-07 16:26 UTC  Andres Freund <andres@anarazel.de>
` Re: BUG #16099: Segmentation fault with - triggers and procedures
  2019-11-07 16:35 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16099: Segmentation fault with - triggers and procedures
  2019-11-07 18:19 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [4+ messages in thread]

BUG #16094: Database entering recovery mode
  2019-11-04 14:50 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16094: Database entering recovery mode
  2019-11-04 15:03 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16094: Database entering recovery mode
  2019-11-06 13:37 UTC  Mircea Pirv <mircea@reva.tech>
` Re: BUG #16094: Database entering recovery mode
  2019-11-07 02:35 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16094: Database entering recovery mode
  2019-11-07 08:07 UTC  Mircea Pirv <mircea@reva.tech>
  [5+ messages in thread]

The XLogFindNextRecord() routine find incorrect record start point after a long continuation record
  2019-11-06 02:40 UTC  Andrey Lepikhov <a.lepikhov@postgrespro.ru>
` Re: The XLogFindNextRecord() routine find incorrect record start point after a long continuation record
  2019-11-06 04:41 UTC  Michael Paquier <michael@paquier.xyz>
` Re: The XLogFindNextRecord() routine find incorrect record start point after a long continuation record
  2019-11-06 05:06 UTC  Andrey Lepikhov <a.lepikhov@postgrespro.ru>
` Re: The XLogFindNextRecord() routine find incorrect record start point after a long continuation record
  2019-11-06 17:41 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: The XLogFindNextRecord() routine find incorrect record start point after a long continuation record
  2019-11-07 03:41 UTC  Michael Paquier <michael@paquier.xyz>
` Re: The XLogFindNextRecord() routine find incorrect record start point after a long continuation record
  2019-11-07 07:37 UTC  Fujii Masao <masao.fujii@gmail.com>
` Re: The XLogFindNextRecord() routine find incorrect record start point after a long continuation record
  2019-11-07 07:52 UTC  Michael Paquier <michael@paquier.xyz>
  [7+ messages in thread]

PostgreSQL 12 installation fails because locale name contained non-english characters
  2019-10-24 11:06 UTC  Skjalg A. Skagen <skjalg.skagen@pm.me>
` Re: PostgreSQL 12 installation fails because locale name contained non-english characters
  2019-11-05 02:48 UTC  Bruce Momjian <bruce@momjian.us>
` Re: PostgreSQL 12 installation fails because locale name contained non-english characters
  2019-11-05 17:22 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL 12 installation fails because locale name contained non-english characters
  2019-11-06 09:30 UTC  Skjalg A. Skagen <skjalg.skagen@pm.me>
` Re: PostgreSQL 12 installation fails because locale name contained non-english characters
  2019-11-06 15:29 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL 12 installation fails because locale name contained non-english characters
  2019-11-06 21:24 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [6+ messages in thread]

BUG #16097: ts_headline fails on text with html style tag
  2019-11-06 15:28 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #16085: Potential missing version information available for /usr/pgsql-12/lib/libpq.so.5
  2019-10-29 07:12 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16085: Potential missing version information available for /usr/pgsql-12/lib/libpq.so.5
  2019-11-06 14:07 UTC  Bruce Momjian <bruce@momjian.us>
` Re: BUG #16085: Potential missing version information available for /usr/pgsql-12/lib/libpq.so.5
  2019-11-06 15:12 UTC  Devrim Gündüz <devrim@gunduz.org>
  [3+ messages in thread]

BUG #16096: psql (non-interactive mode) SQL multi-request commands don't report all feedback ?!
  2019-11-06 11:20 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16096: psql (non-interactive mode) SQL multi-request commands don't report all feedback ?!
  2019-11-06 11:31 UTC  Fabien COELHO <coelho@cri.ensmp.fr>
  [2+ messages in thread]

BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
  2019-07-16 16:26 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
  2019-07-17 16:03 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
  2019-07-26 22:02 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
  2019-07-27 21:41 UTC  Bruce Momjian <bruce@momjian.us>
` Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
  2019-10-09 01:49 UTC  Bruce Momjian <bruce@momjian.us>
` Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
  2019-10-24 18:37 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
  2019-11-05 20:11 UTC  Bruce Momjian <bruce@momjian.us>
  [7+ messages in thread]

Logical replication can be broken by domain constraint with NOT VALID option
  2019-11-03 07:57 UTC  Andrey Lepikhov <a.lepikhov@postgrespro.ru>
` Re: Logical replication can be broken by domain constraint with NOT VALID option
  2019-11-03 15:42 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Logical replication can be broken by domain constraint with NOT VALID option
  2019-11-04 02:32 UTC  Andrey Lepikhov <a.lepikhov@postgrespro.ru>
` Re: Logical replication can be broken by domain constraint with NOT VALID option
  2019-11-05 15:21 UTC  Euler Taveira <euler@timbira.com.br>
` Re: Logical replication can be broken by domain constraint with NOT VALID option
  2019-11-05 17:50 UTC  Andrey Lepikhov <a.lepikhov@postgrespro.ru>
  [5+ messages in thread]

BUG #16075: The favicon of https://www.postgresql.org is vague on MacBook Pro with retina display
  2019-10-24 07:25 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16075: The favicon of https://www.postgresql.org is vague on MacBook Pro with retina display
  2019-11-05 02:41 UTC  Bruce Momjian <bruce@momjian.us>
  [2+ messages in thread]

BUG #16093: Facing the clustering issue while installing the postgres in window10
  2019-11-04 14:07 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16093: Facing the clustering issue while installing the postgres in window10
  2019-11-04 14:43 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: BUG #16093: Facing the clustering issue while installing the postgres in window10
  2019-11-04 23:27 UTC  Gaurav Dubey <gauravdubey89@gmail.com>
` Re: BUG #16093: Facing the clustering issue while installing the postgres in window10
  2019-11-04 23:53 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
  [4+ messages in thread]

ALTER TABLE results in "ERROR: could not open relation with OID 43707388"
  2019-07-04 14:41 UTC  Manuel Rigger <rigger.manuel@gmail.com>
` Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388"
  2019-07-04 16:24 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388"
  2019-07-04 16:40 UTC  Manuel Rigger <rigger.manuel@gmail.com>
` Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388"
  2019-07-04 17:06 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388"
  2019-07-04 17:08 UTC  Manuel Rigger <rigger.manuel@gmail.com>
` Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388"
  2019-07-04 22:50 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388"
  2019-07-04 23:45 UTC  Michael Paquier <michael@paquier.xyz>
` Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388"
  2019-07-05 00:14 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388"
  2019-07-09 17:07 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388"
  2019-11-02 16:04 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388"
  2019-11-03 11:55 UTC  Manuel Rigger <rigger.manuel@gmail.com>
  [11+ messages in thread]

BUG #16016: deadlock with startup process, AccessExclusiveLock on pg_statistic's toast table
  2019-09-20 09:40 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16016: deadlock with startup process, AccessExclusiveLock on pg_statistic's toast table
  2019-09-20 15:00 UTC  Sergei Kornilov <sk@zsrv.org>
` Re: BUG #16016: deadlock with startup process, AccessExclusiveLock on pg_statistic's toast table
  2019-09-22 19:06 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16016: deadlock with startup process, AccessExclusiveLock on pg_statistic's toast table
  2019-11-01 09:15 UTC  Alexey Ermakov <alexey.ermakov@dataegret.com>
` Re: BUG #16016: deadlock with startup process, AccessExclusiveLock on pg_statistic's toast table
  2019-11-01 15:56 UTC  Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #16016: deadlock with startup process, AccessExclusiveLock on pg_statistic's toast table
  2019-11-02 15:10 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16016: deadlock with startup process, AccessExclusiveLock on pg_statistic's toast table
  2019-11-02 17:30 UTC  Alexey Ermakov <alexey.ermakov@dataegret.com>
  [7+ messages in thread]

BUG #16081: pg_upgrade is failed if  a fake cmd.exe exist in the current directory.
  2019-10-26 04:32 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16081: pg_upgrade is failed if  a fake cmd.exe exist in the current directory.
  2019-11-01 22:26 UTC  Daniel Gustafsson <daniel@yesql.se>
  [2+ messages in thread]

BUG #16092: json[b]_to_recordset and json[b]_populate_record do not read properties with mixed-case names
  2019-10-31 14:29 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16092: json[b]_to_recordset and json[b]_populate_record do not read properties with mixed-case names
  2019-10-31 14:41 UTC  Sergei Kornilov <sk@zsrv.org>
  [2+ messages in thread]

a error  happends when create a table in postgresql10.ubuntu 18.04
  2019-10-31 08:12 UTC  ????? <474416133@qq.com>
` Re: a error  happends when create a table in postgresql10.ubuntu 18.04
  2019-10-31 14:41 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
  [2+ messages in thread]

BUG #16082: TOAST's pglz_decompress access to uninitialized data, if  the database is corrupted.
  2019-10-26 07:46 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16082: TOAST's pglz_decompress access to uninitialized data, if  the database is corrupted.
  2019-10-26 21:56 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: BUG #16082: TOAST's pglz_decompress access to uninitialized data, if  the database is corrupted.
  2019-10-30 20:30 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: BUG #16082: TOAST's pglz_decompress access to uninitialized data, if  the database is corrupted.
  2019-10-31 00:00 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
  [4+ messages in thread]

BUG #16090: Migración con pg_dump
  2019-10-30 14:46 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16090: Migración con pg_dump
  2019-10-30 20:51 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
  [2+ messages in thread]

BUG #16091: xpath fails to compute "name()", regression
  2019-10-30 16:58 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16091: xpath fails to compute "name()", regression
  2019-10-30 18:10 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16091: xpath fails to compute "name()", regression
  2019-10-30 20:08 UTC  Cherio <cherio@gmail.com>
  [3+ messages in thread]

memory problems and crash of db when deleting data from table with thousands of partitions
  2019-10-23 11:46 UTC  Josef Machytka <josef.machytka@gmail.com>
` Re: memory problems and crash of db when deleting data from table with thousands of partitions
  2019-10-23 12:47 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: memory problems and crash of db when deleting data from table with thousands of partitions
  2019-10-28 15:18 UTC  Josef Machytka <josef.machytka@gmail.com>
` Re: memory problems and crash of db when deleting data from table with thousands of partitions
  2019-10-28 16:24 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: memory problems and crash of db when deleting data from table with thousands of partitions
  2019-10-30 14:35 UTC  Josef Machytka <josef.machytka@gmail.com>
` Re: memory problems and crash of db when deleting data from table with thousands of partitions
  2019-10-30 18:16 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
  [6+ messages in thread]

BUG #16089: Index only scan does not happen but expected
  2019-10-30 12:54 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16089: Index only scan does not happen but expected
  2019-10-30 14:13 UTC  Dmitry Dolgov <9erthalion6@gmail.com>
` RE: BUG #16089: Index only scan does not happen but expected
  2019-10-30 14:18 UTC  Stepan Yankevych <Stepan_Yankevych@epam.com>
` Re: BUG #16089: Index only scan does not happen but expected
  2019-10-30 15:10 UTC  Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #16089: Index only scan does not happen but expected
  2019-10-30 15:14 UTC  Dmitry Dolgov <9erthalion6@gmail.com>
` RE: BUG #16089: Index only scan does not happen but expected
  2019-10-30 15:27 UTC  Stepan Yankevych <Stepan_Yankevych@epam.com>
  [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