pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #17923: Excessive warnings of collation version mismatch in logs
  2023-05-07 10:13 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17923: Excessive warnings of collation version mismatch in logs
  2023-05-10 05:30 UTC  Peter Eisentraut <peter.eisentraut@enterprisedb.com>
  [2+ messages in thread]

BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and swithing cache->snapshot
  2023-02-22 06:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and swithing cache->snapshot
  2023-02-24 07:08 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and switching cache->snapshot
  2023-02-24 16:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and switching cache->snapshot
  2023-04-27 10:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and switching cache->snapshot
  2023-04-28 01:41 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and switching cache->snapshot
  2023-04-28 04:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and switching cache->snapshot
  2023-04-28 04:37 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and switching cache->snapshot
  2023-04-28 06:04 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and switching cache->snapshot
  2023-04-28 06:06 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and switching cache->snapshot
  2023-04-28 06:48 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and switching cache->snapshot
  2023-04-28 07:07 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and switching cache->snapshot
  2023-05-01 05:18 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and switching cache->snapshot
  2023-05-06 03:28 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17804: Assertion failed in pg_stat after fetching from pg_stat_database and switching cache->snapshot
  2023-05-10 02:26 UTC  Michael Paquier <michael@paquier.xyz>
  [14+ messages in thread]

BUG #17925: Incorrect select query result
  2023-05-08 14:31 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17925: Incorrect select query result
  2023-05-08 19:29 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17925: Incorrect select query result
  2023-05-09 07:00 UTC  Joakim Goldkuhl <joakim.goldkuhl@cogmed.com>
` Re: BUG #17925: Incorrect select query result
  2023-05-09 13:57 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [4+ messages in thread]

AW: [EXTERN] Re: BUG #17921: Packages missing on reposync
  2023-05-08 08:22 UTC  Andreas.Lauger@ergo.de

AW: BUG #17924: Inverted behavior of "Date" and "Reverse Date" when searching a mailbox archive
  2023-05-07 14:11 UTC  Hans Buschmann <buschmann@nidsa.net>

BUG #17924: Inverted behavior of "Date" and "Reverse Date" when searching a mailbox archive
  2023-05-07 10:27 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17924: Inverted behavior of "Date" and "Reverse Date" when searching a mailbox archive
  2023-05-07 14:05 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #17922: ANY vs IN execution plan difference for a single explicit input value
  2023-05-06 20:56 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17922: ANY vs IN execution plan difference for a single explicit input value
  2023-05-07 01:47 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

Bug in tzdata 2022g
  2023-05-06 08:35 UTC  Nacho Caballero <nachocab@gmail.com>
` Re: Bug in tzdata 2022g
  2023-05-06 14:50 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Bug in tzdata 2022g
  2023-05-06 17:10 UTC  Nacho Caballero <nachocab@gmail.com>
  [3+ messages in thread]

Unable to install Application Stack Builder
  2023-05-04 11:59 UTC  Krishnawarriar, Subash <subash.krishna@brambles.com>
` Unable to install Application Stack Builder
  2023-05-04 12:00 UTC  Krishnawarriar, Subash <subash.krishna@brambles.com>
` Re: Unable to install Application Stack Builder
  2023-05-05 08:14 UTC  Aditya Toshniwal <aditya.toshniwal@enterprisedb.com>
` Re: Unable to install Application Stack Builder
  2023-05-05 08:20 UTC  Dave Page <dpage@pgadmin.org>
` Re: Unable to install Application Stack Builder
  2023-05-05 16:16 UTC  Krishnawarriar, Subash <subash.krishna@brambles.com>
` Re: Unable to install Application Stack Builder
  2023-05-06 05:08 UTC  Tony Shelver <tshelver@gmail.com>
  [6+ messages in thread]

BUG #17921: Packages missing on reposync
  2023-05-05 07:12 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17921: Packages missing on reposync
  2023-05-05 13:16 UTC  Devrim Gündüz <devrim@gunduz.org>
  [2+ messages in thread]

BUG #17920: Incorrect memory access in array_position(s) is detected (or not)
  2023-05-04 13:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17920: Incorrect memory access in array_position(s) is detected (or not)
  2023-05-04 15:53 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17920: Incorrect memory access in array_position(s) is detected (or not)
  2023-05-05 03:00 UTC  Alexander Lakhin <exclusion@gmail.com>
  [3+ messages in thread]

BUG #17914: walsenders taking up all memory
  2023-05-01 20:25 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17914: walsenders taking up all memory
  2023-05-03 07:29 UTC  Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17914: walsenders taking up all memory
  2023-05-03 13:38 UTC  Stan S <stashukny@gmail.com>
` Re: BUG #17914: walsenders taking up all memory
  2023-05-04 03:36 UTC  Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #17914: walsenders taking up all memory
  2023-05-04 16:24 UTC  Stan S <stashukny@gmail.com>
  [5+ messages in thread]

 Re: Bug:Create a table with 1600 fields (reaching the upper limit), then drop several fields and create new ones, but the addition failed.
  2023-05-04 16:12 UTC  David G. Johnston <david.g.johnston@gmail.com>

Bug:Create a table with 1600 fields (reaching the upper limit), then drop several fields and create new ones, but the addition failed.
  2023-05-04 15:51 UTC  BO ST <1599224321@qq.com>

BUG #17912: Invalid memory access when converting plpython' array containing empty array
  2023-04-28 11:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array
  2023-04-28 15:14 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array
  2023-04-28 18:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array
  2023-04-28 18:18 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array
  2023-04-28 19:17 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array
  2023-04-29 13:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array
  2023-04-29 17:16 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array
  2023-04-30 04:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array
  2023-04-30 16:24 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array
  2023-05-01 12:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array
  2023-05-04 13:27 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17912: Invalid memory access when converting plpython' array containing empty array
  2023-05-04 15:26 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [12+ messages in thread]

BUG #17918: Checksum failed while sync repos for a package
  2023-05-03 11:43 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17918: Checksum failed while sync repos for a package
  2023-05-03 12:56 UTC  Devrim Gündüz <devrim@gunduz.org>
` Re: BUG #17918: Checksum failed while sync repos for a package
  2023-05-03 22:23 UTC  Devrim Gündüz <devrim@gunduz.org>
  [3+ messages in thread]

BUG #17917: to_tsquery syntax error
  2023-05-03 10:01 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17917: to_tsquery syntax error
  2023-05-03 13:46 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17917: to_tsquery syntax error
  2023-05-03 15:18 UTC  Cyrus Lozano <cyloz28@gmail.com>
  [3+ messages in thread]

BUG #17916: Expression IN list translates to unqualified operator
  2023-05-03 05:19 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17916: Expression IN list translates to unqualified operator
  2023-05-03 13:40 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17916: Expression IN list translates to unqualified operator
  2023-05-03 13:42 UTC  RekGRpth <rekgrpth@gmail.com>
` Re: BUG #17916: Expression IN list translates to unqualified operator
  2023-05-03 14:43 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [4+ messages in thread]

plpython does not honour max-rows
  2023-05-02 10:30 UTC  Kieran McCusker <kieran.mccusker@gmail.com>
` Re: plpython does not honour max-rows
  2023-05-02 11:01 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: plpython does not honour max-rows
  2023-05-02 11:37 UTC  Kieran McCusker <kieran.mccusker@gmail.com>
` Re: plpython does not honour max-rows
  2023-05-02 11:48 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: plpython does not honour max-rows
  2023-05-02 11:51 UTC  Kieran McCusker <kieran.mccusker@gmail.com>
` Re: plpython does not honour max-rows
  2023-05-02 14:02 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: plpython does not honour max-rows
  2023-05-02 20:34 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: plpython does not honour max-rows
  2023-05-02 20:35 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: plpython does not honour max-rows
  2023-05-02 20:39 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: plpython does not honour max-rows
  2023-05-02 20:50 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: plpython does not honour max-rows
  2023-05-02 21:21 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: plpython does not honour max-rows
  2023-05-02 21:23 UTC  Daniel Gustafsson <daniel@yesql.se>
  [12+ messages in thread]

BUG #17915: sha256sum check failure on postgress 14 rhel-7-x86_64 repository
  2023-05-02 16:58 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #17906: Segmentation fault and database crash during procedure call
  2023-04-21 10:19 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17906: Segmentation fault and database crash during procedure call
  2023-04-21 14:09 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17906: Segmentation fault and database crash during procedure call
  2023-05-01 07:40 UTC  Michael Paquier <michael@paquier.xyz>
` RE: BUG #17906: Segmentation fault and database crash during procedure call
  2023-05-02 12:00 UTC  Vaclav Pink <vaclav.pink@tietoevry.com>
` Re: BUG #17906: Segmentation fault and database crash during procedure call
  2023-05-02 16:29 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [5+ messages in thread]

BUG #17913: alter column set (n_distinct=...) on partition head doesn't work for declarative partitioned tables
  2023-04-30 03:20 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17913: alter column set (n_distinct=...) on partition head doesn't work for declarative partitioned tables
  2023-05-01 04:40 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17913: alter column set (n_distinct=...) on partition head doesn't work for declarative partitioned tables
  2023-05-01 04:46 UTC  Maxim Boguk <maxim.boguk@gmail.com>
  [3+ messages in thread]

BUG #17909: CREATE SCHEMA AUTHORIZATION sch CREATE TABLE foo ( id INT )  will coredump
  2023-04-27 03:44 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17909: CREATE SCHEMA AUTHORIZATION sch CREATE TABLE foo ( id INT )  will coredump
  2023-04-27 07:34 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17909: CREATE SCHEMA AUTHORIZATION sch CREATE TABLE foo ( id INT ) will coredump
  2023-04-27 08:59 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17909: CREATE SCHEMA AUTHORIZATION sch CREATE TABLE foo ( id INT ) will coredump
  2023-04-27 09:31 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17909: CREATE SCHEMA AUTHORIZATION sch CREATE TABLE foo ( id INT ) will coredump
  2023-04-27 10:28 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17909: CREATE SCHEMA AUTHORIZATION sch CREATE TABLE foo ( id INT ) will coredump
  2023-04-27 23:05 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17909: CREATE SCHEMA AUTHORIZATION sch CREATE TABLE foo ( id INT ) will coredump
  2023-04-27 23:48 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17909: CREATE SCHEMA AUTHORIZATION sch CREATE TABLE foo ( id INT ) will coredump
  2023-04-27 23:56 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17909: CREATE SCHEMA AUTHORIZATION sch CREATE TABLE foo ( id INT ) will coredump
  2023-04-28 01:42 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17909: CREATE SCHEMA AUTHORIZATION sch CREATE TABLE foo ( id INT ) will coredump
  2023-04-28 03:29 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17909: CREATE SCHEMA AUTHORIZATION sch CREATE TABLE foo ( id INT ) will coredump
  2023-04-28 03:56 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17909: CREATE SCHEMA AUTHORIZATION sch CREATE TABLE foo ( id INT ) will coredump
  2023-04-28 04:53 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17909: CREATE SCHEMA AUTHORIZATION sch CREATE TABLE foo ( id INT ) will coredump
  2023-04-28 05:07 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17909: CREATE SCHEMA AUTHORIZATION sch CREATE TABLE foo ( id INT ) will coredump
  2023-04-30 22:09 UTC  Michael Paquier <michael@paquier.xyz>
  [14+ messages in thread]

BUG #16628: Hostame and string connection functions
  2020-09-22 18:57 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16628: Hostame and string connection functions
  2020-09-24 21:07 UTC  Bruce Momjian <bruce@momjian.us>
` Re: BUG #16628: Hostame and string connection functions
  2023-04-22 14:57 UTC  Anderson Antunes <anderson.ant.oli@gmail.com>
` Re: BUG #16628: Hostame and string connection functions
  2023-04-28 18:47 UTC  Bruce Momjian <bruce@momjian.us>
` Re: BUG #16628: Hostame and string connection functions
  2023-04-28 19:59 UTC  Anderson Antunes <anderson.ant.oli@gmail.com>
  [5+ messages in thread]

BUG #17903: There is a bug in the KeepLogSeg()
  2023-04-19 10:26 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17903: There is a bug in the KeepLogSeg()
  2023-04-20 03:04 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17903: There is a bug in the KeepLogSeg()
  2023-04-20 07:40 UTC  Junwang Zhao <zhjwpku@gmail.com>
` Re: BUG #17903: There is a bug in the KeepLogSeg()
  2023-04-20 08:58 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17903: There is a bug in the KeepLogSeg()
  2023-04-20 11:17 UTC  Junwang Zhao <zhjwpku@gmail.com>
` Re: BUG #17903: There is a bug in the KeepLogSeg()
  2023-04-20 22:02 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #17903: There is a bug in the KeepLogSeg()
  2023-04-21 01:42 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17903: There is a bug in the KeepLogSeg()
  2023-04-21 21:43 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #17903: There is a bug in the KeepLogSeg()
  2023-04-24 19:14 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #17903: There is a bug in the KeepLogSeg()
  2023-04-25 04:14 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17903: There is a bug in the KeepLogSeg()
  2023-04-27 21:47 UTC  Nathan Bossart <nathandbossart@gmail.com>
` Re: BUG #17903: There is a bug in the KeepLogSeg()
  2023-04-27 23:08 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17903: There is a bug in the KeepLogSeg()
  2023-04-28 06:21 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
  [13+ 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