pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #16306: cluster error
  2020-03-17 15:33 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16306: cluster error
  2020-03-25 05:08 UTC  Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
  [2+ messages in thread]

BUG #16310: Database Cluster Initialization failed while installing postgres
  2020-03-22 08:35 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16310: Database Cluster Initialization failed while installing postgres
  2020-03-22 08:53 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #16310: Database Cluster Initialization failed while installing postgres
  2020-03-22 09:21 UTC  Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #16310: Database Cluster Initialization failed while installing postgres
  2020-03-25 05:06 UTC  Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
  [4+ messages in thread]

handle tablespaces for partitioned tables during ALTER DATABASE
  2020-03-24 06:26 UTC  postgres@jasonk.me
` Re: handle tablespaces for partitioned tables during ALTER DATABASE
  2020-03-24 19:23 UTC  Andres Freund <andres@anarazel.de>
` Fwd: Re: handle tablespaces for partitioned tables during ALTER DATABASE
  2020-03-25 03:31 UTC  postgres@jasonk.me
  [3+ messages in thread]

Postgresql create a core while trying log a message to syslog
  2020-03-11 18:24 UTC  Demarest, Jamie <Jamie.Demarest@saabsensis.com>
` Re: Postgresql create a core while trying log a message to syslog
  2020-03-11 22:14 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: Postgresql create a core while trying log a message to syslog
  2020-03-11 22:39 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` RE: Postgresql create a core while trying log a message to syslog
  2020-03-12 14:35 UTC  Demarest, Jamie <Jamie.Demarest@saabsensis.com>
` RE: Postgresql create a core while trying log a message to syslog
  2020-03-19 12:48 UTC  Demarest, Jamie <Jamie.Demarest@saabsensis.com>
` Re: Postgresql create a core while trying log a message to syslog
  2020-03-24 14:59 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
  [6+ messages in thread]

BUG #16305: Application Stack Builder downloads MacOS JDBC binary
  2020-03-17 02:44 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16305: Application Stack Builder downloads MacOS JDBC binary
  2020-03-24 04:42 UTC  Fahar Abbas <fahar.abbas@enterprisedb.com>
` Re: BUG #16305: Application Stack Builder downloads MacOS JDBC binary
  2020-03-24 05:35 UTC  Maegawa Yoshihiro(前川 喜洋) <y.maegawa.yc@future.co.jp>
  [3+ messages in thread]

BUG #16313: [2528] ERROR:  column pd.adsrc does not exist at character 89
  2020-03-24 04:02 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16313: [2528] ERROR: column pd.adsrc does not exist at character 89
  2020-03-24 04:11 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [2+ messages in thread]

BUG #16312: How to get last modified timestamp of password change for user in postgresql.
  2020-03-23 22:31 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16312: How to get last modified timestamp of password change for user in postgresql.
  2020-03-24 00:46 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [2+ messages in thread]

BUG #16311: Zero sized WAL archive logs on DAS
  2020-03-23 16:27 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #16304: ECPG won't accept input from STDIN
  2020-03-16 20:48 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16304: ECPG won't accept input from STDIN
  2020-03-23 02:45 UTC  Bruce Momjian <bruce@momjian.us>
` Re: BUG #16304: ECPG won't accept input from STDIN
  2020-03-23 04:20 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

BUG #16309: Postgres's ISO 8601 date output is not compliant
  2020-03-20 19:26 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16309: Postgres's ISO 8601 date output is not compliant
  2020-03-20 20:09 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [2+ messages in thread]

BUG #16302: too many range table entries - when count partition table(65538 childs)
  2020-03-14 14:02 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16302: too many range table entries - when count partition table(65538 childs)
  2020-03-14 15:03 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16302: too many range table entries - when count partition table(65538 childs)
  2020-03-16 02:27 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #16302: too many range table entries - when count partition table(65538 childs)
  2020-03-16 02:38 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16302: too many range table entries - when count partition table(65538 childs)
  2020-03-17 11:42 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: BUG #16302: too many range table entries - when count partition table(65538 childs)
  2020-03-17 13:48 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16302: too many range table entries - when count partition table(65538 childs)
  2020-03-17 14:33 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: BUG #16302: too many range table entries - when count partition table(65538 childs)
  2020-03-17 14:42 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16302: too many range table entries - when count partition table(65538 childs)
  2020-03-17 15:04 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: BUG #16302: too many range table entries - when count partition table(65538 childs)
  2020-03-19 11:04 UTC  Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
` Re: BUG #16302: too many range table entries - when count partition table(65538 childs)
  2020-03-19 13:33 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16302: too many range table entries - when count partition table(65538 childs)
  2020-03-20 02:21 UTC  Robert Haas <robertmhaas@gmail.com>
  [12+ messages in thread]

Trigger does not work after partitioning
  2020-03-19 16:44 UTC  Raschkowski, Michael <michael.raschkowski@auconet-it.com>
` Re: Trigger does not work after partitioning
  2020-03-19 17:42 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
  [2+ messages in thread]

Optimizer Doesn't Push Down Where Expressions on Rollups
  2020-03-09 21:05 UTC  Logan Bowers <logan.bowers@gmail.com>
` Re: Optimizer Doesn't Push Down Where Expressions on Rollups
  2020-03-11 08:59 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: Optimizer Doesn't Push Down Where Expressions on Rollups
  2020-03-11 14:06 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Optimizer Doesn't Push Down Where Expressions on Rollups
  2020-03-11 16:58 UTC  Logan Bowers <logan.bowers@gmail.com>
` Re: Optimizer Doesn't Push Down Where Expressions on Rollups
  2020-03-12 10:22 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: Optimizer Doesn't Push Down Where Expressions on Rollups
  2020-03-19 09:28 UTC  Richard Guo <guofenglinux@gmail.com>
  [6+ messages in thread]

windows 10 postgres install bug
  2020-02-19 00:41 UTC  Doke, Tim (TR Tech, Content & Ops) <tim.doke@thomsonreuters.com>
` Re: windows 10 postgres install bug
  2020-03-19 09:16 UTC  Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
  [2+ messages in thread]

BUG #16270: Repository URL is wrong
  2020-02-21 09:25 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16270: Repository URL is wrong
  2020-03-18 22:17 UTC  Bruce Momjian <bruce@momjian.us>
  [2+ messages in thread]

BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR:  unrecognized configuration parameter "i
  2020-03-18 12:12 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR:  unrecognized configuration parameter "i
  2020-03-18 12:49 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR: unrecognized configuration parameter "i
  2020-03-18 14:20 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16308: pg_restore: [archiver (db)] could not execute query: ERROR: unrecognized configuration parameter "i
  2020-03-18 15:07 UTC  Daniel Gustafsson <daniel@yesql.se>
  [4+ messages in thread]

pg_dump No comment for policy
  2020-02-16 21:41 UTC  Marc Munro <marc@bloodnok.com>
` Re: pg_dump No comment for policy
  2020-02-17 17:59 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump No comment for policy
  2020-03-18 02:19 UTC  Bruce Momjian <bruce@momjian.us>
  [3+ messages in thread]

BUG #16303: A condtion whether an index-only scan is possible includes a wrong
  2020-03-16 06:02 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16303: A condtion whether an index-only scan is possible includes a wrong
  2020-03-16 06:05 UTC  Horimoto Yasuhiro <horimoto@clear-code.com>
` Re: BUG #16303: A condtion whether an index-only scan is possible includes a wrong
  2020-03-16 06:35 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #16303: A condtion whether an index-only scan is possible includes a wrong
  2020-03-16 08:22 UTC  Horimoto Yasuhiro <horimoto@clear-code.com>
` Re: BUG #16303: A condtion whether an index-only scan is possible includes a wrong
  2020-03-16 15:20 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16303: A condtion whether an index-only scan is possible includes a wrong
  2020-03-18 00:34 UTC  Horimoto Yasuhiro <horimoto@clear-code.com>
  [6+ messages in thread]

BUG #16280: dead tuples (probably) effect plan and query performance
  2020-02-27 11:28 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16280: dead tuples (probably) effect plan and query performance
  2020-02-27 14:07 UTC  Alexey Ermakov <alexey.ermakov@dataegret.com>
` Re: BUG #16280: dead tuples (probably) effect plan and query performance
  2020-02-27 15:41 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16280: dead tuples (probably) effect plan and query performance
  2020-02-28 09:25 UTC  Serbin, Ilya <iserbin@bostonsd.ru>
` Re: BUG #16280: dead tuples (probably) effect plan and query performance
  2020-03-11 10:50 UTC  Serbin, Ilya <iserbin@bostonsd.ru>
` Re: BUG #16280: dead tuples (probably) effect plan and query performance
  2020-03-11 13:01 UTC  James Coleman <jtc331@gmail.com>
` Re: BUG #16280: dead tuples (probably) effect plan and query performance
  2020-03-17 17:36 UTC  Serbin, Ilya <iserbin@bostonsd.ru>
  [7+ messages in thread]

BUG #16103: Initdb does not respect country for language
  2019-11-08 12:14 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16103: Initdb does not respect country for language
  2019-11-13 06:10 UTC  Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` Re: BUG #16103: Initdb does not respect country for language
  2019-11-13 06:19 UTC  Fahar Abbas <fahar.abbas@enterprisedb.com>
` Re: BUG #16103: Initdb does not respect country for language
  2019-11-13 07:05 UTC  Fahar Abbas <fahar.abbas@enterprisedb.com>
` Re: BUG #16103: Initdb does not respect country for language
  2020-03-17 07:31 UTC  Fahar Abbas <fahar.abbas@enterprisedb.com>
` Re: BUG #16103: Initdb does not respect country for language
  2020-03-17 07:33 UTC  Fahar Abbas <fahar.abbas@enterprisedb.com>
` Re: BUG #16103: Initdb does not respect country for language
  2020-03-17 11:00 UTC  Fahar Abbas <fahar.abbas@enterprisedb.com>
` Re: BUG #16103: Initdb does not respect country for language
  2020-03-17 11:30 UTC  Fahar Abbas <fahar.abbas@enterprisedb.com>
  [8+ messages in thread]

AW: BUG #16103: Initdb does not respect country for language
  2020-02-05 08:58 UTC  Wimmesberger, Simon <simon.wimmesberger@zoetis.com>
` AW: BUG #16103: Initdb does not respect country for language
  2020-03-17 08:25 UTC  Wimmesberger, Simon <simon.wimmesberger@zoetis.com>
` AW: BUG #16103: Initdb does not respect country for language
  2020-03-17 11:11 UTC  Wimmesberger, Simon <simon.wimmesberger@zoetis.com>
  [3+ messages in thread]

duplicate key value violates unique constraint "tableName_pk"
  2012-11-07 11:21 UTC  Saravanan Nagarajan <n.saravanan86@gmail.com>
` Re: duplicate key value violates unique constraint "tableName_pk"
  2012-11-07 17:21 UTC  Pavan Deolasee <pavan.deolasee@gmail.com>
` Re: duplicate key value violates unique constraint "tableName_pk"
  2012-11-08 02:19 UTC  Craig Ringer <ringerc@ringerc.id.au>
` Duplicate key value violates unique constraint
  2020-03-16 15:55 UTC  Nafees Sardar <nafees@epazz.net>
` Re: Duplicate key value violates unique constraint
  2020-03-16 16:23 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Duplicate key value violates unique constraint
  2020-03-16 16:27 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [6+ messages in thread]

BUG #16301: unable to connect to server
  2020-03-14 03:39 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16301: unable to connect to server
  2020-03-14 03:50 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #16301: unable to connect to server
  2020-03-14 04:15 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [3+ messages in thread]

BUG #16300: Text line order corruption with COPY command
  2020-03-12 20:04 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16300: Text line order corruption with COPY command
  2020-03-12 20:42 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #16300: Text line order corruption with COPY command
  2020-03-13 09:26 UTC  Francisco Olarte <folarte@peoplecall.com>
` Re: BUG #16300: Text line order corruption with COPY command
  2020-03-13 15:19 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [4+ messages in thread]

AW: BUG #16300: Text line order corruption with COPY command
  2020-03-13 08:49 UTC  Hans Buschmann <buschmann@nidsa.net>


[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