pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #16358: formas web site sql
  2020-04-13 14:58 UTC  PG Bug reporting form <noreply@postgresql.org>

[bug] Wrong bool value parameter
  2020-04-07 09:30 UTC  曾文旌 <wjzeng2012@gmail.com>
` Re: [bug] Wrong bool value parameter
  2020-04-07 11:58 UTC  Euler Taveira <euler.taveira@2ndquadrant.com>
` Re: [bug] Wrong bool value parameter
  2020-04-07 14:35 UTC  Masahiko Sawada <masahiko.sawada@2ndquadrant.com>
` Re: [bug] Wrong bool value parameter
  2020-04-08 07:00 UTC  wenjing <wjzeng2012@gmail.com>
` Re: [bug] Wrong bool value parameter
  2020-04-08 12:25 UTC  Masahiko Sawada <masahiko.sawada@2ndquadrant.com>
` Re: [bug] Wrong bool value parameter
  2020-04-08 13:45 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: [bug] Wrong bool value parameter
  2020-04-11 14:54 UTC  wenjing <wjzeng2012@gmail.com>
` Re: [bug] Wrong bool value parameter
  2020-04-11 15:05 UTC  wenjing <wjzeng2012@gmail.com>
` Re: [bug] Wrong bool value parameter
  2020-04-11 15:25 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [9+ messages in thread]

BUG #16357: Incorrect rounding for negative arguments in to_timestamp()
  2020-04-11 06:01 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #16355: (packaging) [pgdg12-source] is used multiple times in /etc/yum.repos.d/pgdg-redhat-all.repo
  2020-04-10 08:29 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16355: (packaging) [pgdg12-source] is used multiple times in /etc/yum.repos.d/pgdg-redhat-all.repo
  2020-04-11 00:50 UTC  Devrim Gündüz <devrim@gunduz.org>
  [2+ messages in thread]

BUG #16349: pgbouncer missing from repo
  2020-04-08 01:24 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16349: pgbouncer missing from repo
  2020-04-11 00:33 UTC  Devrim Gündüz <devrim@gunduz.org>
  [2+ messages in thread]

Re: BUG #16356: Can't perform json operations on casted text in where clause when a join is used. WHERE is too early
  2020-04-10 21:12 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16356: Can't perform json operations on casted text in where clause when a join is used. WHERE is too early
  2020-04-10 21:13 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [2+ messages in thread]

pg_tables anomalies
  2020-04-10 08:21 UTC  ribal <na97oribal@gmail.com>
` Re: pg_tables anomalies
  2020-04-10 13:41 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

Loss of replication after simple misconfiguration
  2020-04-09 14:08 UTC  hubert depesz lubaczewski <depesz@depesz.com>
` Re: Loss of replication after simple misconfiguration
  2020-04-09 16:19 UTC  Andrew Gierth <andrew@tao11.riddles.org.uk>
` Re: Loss of replication after simple misconfiguration
  2020-04-09 16:48 UTC  Victor Yegorov <vyegorov@gmail.com>
` Re: Loss of replication after simple misconfiguration
  2020-04-10 04:14 UTC  Michael Paquier <michael@paquier.xyz>
` Re: Loss of replication after simple misconfiguration
  2020-04-10 05:43 UTC  Michael Paquier <michael@paquier.xyz>
` Re: Loss of replication after simple misconfiguration
  2020-04-10 07:26 UTC  hubert depesz lubaczewski <depesz@depesz.com>
` Re: Loss of replication after simple misconfiguration
  2020-04-10 07:59 UTC  Michael Paquier <michael@paquier.xyz>
` Re: Loss of replication after simple misconfiguration
  2020-04-10 08:01 UTC  hubert depesz lubaczewski <depesz@depesz.com>
  [8+ messages in thread]

BUG #16345: ts_headline does not find phrase matches correctly
  2020-04-05 21:49 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16345: ts_headline does not find phrase matches correctly
  2020-04-09 03:02 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16345: ts_headline does not find phrase matches correctly
  2020-04-09 18:39 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: BUG #16345: ts_headline does not find phrase matches correctly
  2020-04-09 19:29 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [4+ messages in thread]

BUG #16351: PostgreSQL closing connection during requests with segmentation fault
  2020-04-08 08:55 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault
  2020-04-08 12:15 UTC  Hamid Akhtar <hamid.akhtar@gmail.com>
` Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault
  2020-04-08 13:52 UTC  Daniele Varrazzo <daniele.varrazzo@gmail.com>
` Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault
  2020-04-08 13:56 UTC  Johannes Mols <johannes.mols@gmail.com>
` Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault
  2020-04-08 14:10 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault
  2020-04-08 14:58 UTC  Johannes Mols <johannes.mols@gmail.com>
` Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault
  2020-04-09 01:48 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault
  2020-04-09 09:35 UTC  Johannes Mols <johannes.mols@gmail.com>
` Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault
  2020-04-09 13:40 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault
  2020-04-09 15:58 UTC  Daniel Verite <daniel@manitou-mail.org>
` Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault
  2020-04-09 17:42 UTC  Johannes Mols <johannes.mols@gmail.com>
  [11+ messages in thread]

BUG #16342: CREATE TABLE LIKE INCLUDING GENERATED column order issue
  2020-04-03 23:50 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16342: CREATE TABLE LIKE INCLUDING GENERATED column order issue
  2020-04-05 11:28 UTC  Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
` Re: BUG #16342: CREATE TABLE LIKE INCLUDING GENERATED column order issue
  2020-04-05 15:26 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16342: CREATE TABLE LIKE INCLUDING GENERATED column order issue
  2020-04-09 14:48 UTC  Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
` RE: BUG #16342: CREATE TABLE LIKE INCLUDING GENERATED column order issue
  2020-04-09 14:55 UTC  Ethan Waldo <ewaldo@healthetechs.com>
  [5+ messages in thread]

BUG #16353: pg_isready timeout is ignored
  2020-04-09 06:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16353: pg_isready timeout is ignored
  2020-04-09 07:45 UTC  Hamid Akhtar <hamid.akhtar@gmail.com>
  [2+ messages in thread]

why wal_max_size does not work?
  2020-03-24 12:06 UTC  Fan Liu <fan.liu@ericsson.com>
` Re: why wal_max_size does not work?
  2020-03-24 12:32 UTC  Sergei Kornilov <sk@zsrv.org>
` RE: why wal_max_size does not work?
  2020-03-27 06:10 UTC  Fan Liu <fan.liu@ericsson.com>
` Re: why wal_max_size does not work?
  2020-03-27 06:36 UTC  Jaime Casanova <jaime.casanova@2ndquadrant.com>
` RE: why wal_max_size does not work?
  2020-03-27 07:12 UTC  Fan Liu <fan.liu@ericsson.com>
` RE: why wal_max_size does not work?
  2020-03-31 01:24 UTC  Fan Liu <fan.liu@ericsson.com>
` RE: why wal_max_size does not work?
  2020-04-01 06:51 UTC  Fan Liu <fan.liu@ericsson.com>
` RE: why wal_max_size does not work?
  2020-04-09 01:45 UTC  Fan Liu <fan.liu@ericsson.com>
  [8+ messages in thread]

ERROR: cannot pass more than 100 arguments to a function
  2020-04-08 21:04 UTC  Ján Máté <jan.mate@inf-it.com>
` Re: ERROR: cannot pass more than 100 arguments to a function
  2020-04-08 21:34 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: ERROR: cannot pass more than 100 arguments to a function
  2020-04-08 21:34 UTC  raf <raf@raf.org>
  [3+ messages in thread]

BUG #16348: Memory leak when parsing config
  2020-04-07 13:36 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16348: Memory leak when parsing config
  2020-04-07 15:22 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16348: Memory leak when parsing config
  2020-04-08 06:51 UTC  Hugh Wang <hghwng@gmail.com>
` Re: BUG #16348: Memory leak when parsing config
  2020-04-08 19:25 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [4+ messages in thread]

BUG #16346: pg_upgrade fails on a trigger with a comment
  2020-04-06 15:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16346: pg_upgrade fails on a trigger with a comment
  2020-04-07 20:10 UTC  Hamid Akhtar <hamid.akhtar@gmail.com>
` Re: BUG #16346: pg_upgrade fails on a trigger with a comment
  2020-04-08 07:21 UTC  Hamid Akhtar <hamid.akhtar@gmail.com>
` Re: BUG #16346: pg_upgrade fails on a trigger with a comment
  2020-04-08 15:34 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [4+ messages in thread]

BUG #16350: pgcenter expects postgresql12-libs on postgresql 11
  2020-04-08 08:39 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16350: pgcenter expects postgresql12-libs on postgresql 11
  2020-04-08 12:23 UTC  Alexey Lesovsky <alexey.lesovsky@dataegret.com>
` Re: BUG #16350: pgcenter expects postgresql12-libs on postgresql 11
  2020-04-08 12:27 UTC  Hamid Akhtar <hamid.akhtar@gmail.com>
  [3+ messages in thread]

BUG #16325: Assert failure on partitioning by int for a text value with a collation
  2020-03-28 05:43 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16325: Assert failure on partitioning by int for a text value with a collation
  2020-03-28 12:53 UTC  Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #16325: Assert failure on partitioning by int for a text value with a collation
  2020-04-01 07:08 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16325: Assert failure on partitioning by int for a text value with a collation
  2020-04-01 12:01 UTC  Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #16325: Assert failure on partitioning by int for a text value with a collation
  2020-04-02 02:01 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16325: Assert failure on partitioning by int for a text value with a collation
  2020-04-03 15:29 UTC  Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #16325: Assert failure on partitioning by int for a text value with a collation
  2020-04-07 07:49 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16325: Assert failure on partitioning by int for a text value with a collation
  2020-04-08 06:06 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #16325: Assert failure on partitioning by int for a text value with a collation
  2020-04-08 08:20 UTC  Dmitry Dolgov <9erthalion6@gmail.com>
  [9+ messages in thread]

BUG #16347: pgbadger is missing in the repo
  2020-04-07 13:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16347: pgbadger is missing in the repo
  2020-04-08 01:14 UTC  Devrim Gündüz <devrim@gunduz.org>
  [2+ messages in thread]

Don't try fetching future segment of a TLI.
  2020-01-29 03:02 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Don't try fetching future segment of a TLI.
  2020-02-01 05:31 UTC  David Steele <david@pgmasters.net>
` Re: Don't try fetching future segment of a TLI.
  2020-03-19 13:22 UTC  Pavel Suderevsky <psuderevsky@gmail.com>
` Re: Don't try fetching future segment of a TLI.
  2020-04-06 17:43 UTC  Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: Don't try fetching future segment of a TLI.
  2020-04-06 19:04 UTC  David Steele <david@pgmasters.net>
` Re: Don't try fetching future segment of a TLI.
  2020-04-07 01:29 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Don't try fetching future segment of a TLI.
  2020-04-07 03:15 UTC  Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: Don't try fetching future segment of a TLI.
  2020-04-07 03:22 UTC  Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: Don't try fetching future segment of a TLI.
  2020-04-07 07:48 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Don't try fetching future segment of a TLI.
  2020-04-07 08:17 UTC  Michael Paquier <michael@paquier.xyz>
` Re: Don't try fetching future segment of a TLI.
  2020-04-07 09:36 UTC  Grigory Smolkin <g.smolkin@postgrespro.ru>
` Re: Don't try fetching future segment of a TLI.
  2020-04-07 11:21 UTC  David Steele <david@pgmasters.net>
` Re: Don't try fetching future segment of a TLI.
  2020-04-07 16:49 UTC  Fujii Masao <masao.fujii@oss.nttdata.com>
  [13+ messages in thread]

BUG #16336: Undefined symbols since upgrade of VS to 2019.5.2, and other issues
  2020-04-02 09:58 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16336: Undefined symbols since upgrade of VS to 2019.5.2, and other issues
  2020-04-02 11:59 UTC  Mario Emmenlauer <mario@emmenlauer.de>
` Re: BUG #16336: Undefined symbols since upgrade of VS to 2019.5.2, and other issues
  2020-04-06 14:06 UTC  Mario Emmenlauer <mario@emmenlauer.de>
  [3+ messages in thread]

Postgres Installer not Appearing When Exe Is Run
  2020-04-02 00:51 UTC  Doug Johnson <Doug.D.Johnson@ey.com>
` Re: Postgres Installer not Appearing When Exe Is Run
  2020-04-06 12:30 UTC  Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
  [2+ messages in thread]

BUG #16344: json_agg slow performance vs jsonb_agg, truncate table for master table with remote partition
  2020-04-05 21:08 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #16333: position() function not equivalent to strpos() function when comparing citext
  2020-04-01 23:26 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16333: position() function not equivalent to strpos() function when comparing citext
  2020-04-02 01:00 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #16333: position() function not equivalent to strpos() function when comparing citext
  2020-04-02 01:04 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16333: position() function not equivalent to strpos() function when comparing citext
  2020-04-02 20:53 UTC  Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
` Re: BUG #16333: position() function not equivalent to strpos() function when comparing citext
  2020-04-02 21:46 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16333: position() function not equivalent to strpos() function when comparing citext
  2020-04-05 10:41 UTC  Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
  [6+ messages in thread]

BUG #16334: We recently upgraded PG version from 9.5 to 10.10 and system performance is not so good
  2020-04-02 03:52 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16334: We recently upgraded PG version from 9.5 to 10.10 and system performance is not so good
  2020-04-02 08:46 UTC  Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #16334: We recently upgraded PG version from 9.5 to 10.10 and system performance is not so good
  2020-04-02 10:22 UTC  Tejaswini GC <tejaswini.gc@decathlon.com>
` Re: BUG #16334: We recently upgraded PG version from 9.5 to 10.10 and system performance is not so good
  2020-04-02 11:04 UTC  Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #16334: We recently upgraded PG version from 9.5 to 10.10 and system performance is not so good
  2020-04-02 11:09 UTC  Tejaswini GC <tejaswini.gc@decathlon.com>
` Re: BUG #16334: We recently upgraded PG version from 9.5 to 10.10 and system performance is not so good
  2020-04-04 06:27 UTC  Tejaswini GC <tejaswini.gc@decathlon.com>
` Re: BUG #16334: We recently upgraded PG version from 9.5 to 10.10 and system performance is not so good
  2020-04-04 07:06 UTC  Julien Rouhaud <rjuju123@gmail.com>
  [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