pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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]

BUG #17908: plpython_to_hstore() crashes with a non-dict argument
  2023-04-25 13:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17908: plpython_to_hstore() crashes with a non-dict argument
  2023-04-27 08:27 UTC  Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #17908: plpython_to_hstore() crashes with a non-dict argument
  2023-04-27 14:46 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

BUG #17910: gcc-introduced load may cause concurrency bug
  2023-04-27 08:45 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17910: gcc-introduced load may cause concurrency bug
  2023-04-27 09:01 UTC  Daniel Gustafsson <daniel@yesql.se>
  [2+ messages in thread]

BUG #17907: PostgresSQL 15.x contains OpenSSL DLLs (vulnerable to CVE-2023-0464, CVE-2023-0465 & CVE-2023-0466)
  2023-04-24 14:34 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17907: PostgresSQL 15.x contains OpenSSL DLLs (vulnerable to CVE-2023-0464, CVE-2023-0465 & CVE-2023-0466)
  2023-04-27 07:43 UTC  Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
  [2+ messages in thread]

[PATCH v3 1/1] Prevent underflow in KeepLogSeg().
  2023-04-24 18:29 UTC  Nathan Bossart <nbossart@postgresql.org>

BUG #17847: Unaligned memory access in ltree_gist
  2023-03-16 18:00 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-03-16 19:35 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-03-18 07:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-03-19 17:08 UTC  Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-03-19 17:09 UTC  Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-03-20 07:00 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-04-18 10:16 UTC  Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-04-18 10:34 UTC  Pavel Borisov <pashkin.elfe@gmail.com>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-04-18 10:57 UTC  Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-04-18 11:11 UTC  Pavel Borisov <pashkin.elfe@gmail.com>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-04-18 11:16 UTC  Pavel Borisov <pashkin.elfe@gmail.com>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-04-18 11:43 UTC  Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-04-18 15:06 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-04-18 15:19 UTC  Pavel Borisov <pashkin.elfe@gmail.com>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-04-18 15:25 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-04-19 16:26 UTC  Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-04-19 16:47 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-04-19 16:59 UTC  Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-04-19 18:56 UTC  Pavel Borisov <pashkin.elfe@gmail.com>
` Re: BUG #17847: Unaligned memory access in ltree_gist
  2023-04-23 11:32 UTC  Alexander Korotkov <aekorotkov@gmail.com>
  [20+ messages in thread]

BUG #17905: phpPgAdmin 7.13.0 is not updated to support PHP 8.1.16
  2023-04-21 03:09 UTC  PG Bug reporting form <noreply@postgresql.org>

Assert failure with ICU support
  2023-04-19 10:30 UTC  Richard Guo <guofenglinux@gmail.com>
` Re: Assert failure with ICU support
  2023-04-19 15:42 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Assert failure with ICU support
  2023-04-19 20:31 UTC  Jeff Davis <pgsql@j-davis.com>
` Re: Assert failure with ICU support
  2023-04-19 20:45 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Assert failure with ICU support
  2023-04-20 19:47 UTC  Jeff Davis <pgsql@j-davis.com>
` Re: Assert failure with ICU support
  2023-04-20 19:53 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Assert failure with ICU support
  2023-04-20 23:30 UTC  Jeff Davis <pgsql@j-davis.com>
` Re: Assert failure with ICU support
  2023-04-20 23:31 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [8+ messages in thread]

BUG #17898: Build failure when strip is LLVM's version
  2023-04-15 03:45 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17898: Build failure when strip is LLVM's version
  2023-04-20 22:15 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #15710: ADD COLUMN IF NOT EXISTS adds constraint anyways
  2019-03-21 08:41 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #15710: ADD COLUMN IF NOT EXISTS adds constraint anyways
  2019-03-21 14:18 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #15710: ADD COLUMN IF NOT EXISTS adds constraint anyways
  2019-03-22 08:36 UTC  Christoph Berg <myon@debian.org>
` [PATCH] Fix incorrect calculation regarding max_slot_wal_keep_size
  2023-04-20 02:51 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` [PATCH v2] Fix incorrect calculation regarding max_slot_wal_keep_size
  2023-04-20 02:51 UTC  Kyotaro Horiguchi <horikyota.ntt@gmail.com>
  [5+ messages in thread]

BUG #17904: Inconsistent value of max_worker_processes parameter in the config file and running cluster
  2023-04-19 19:54 UTC  PG Bug reporting form <noreply@postgresql.org>

About #13489
  2023-04-19 09:35 UTC  Bruno Bonfils <asyd@asyd.net>

BUG #17901: Unexpected 'permission denied' error depending on which template used to create database
  2023-04-17 11:33 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17901: Unexpected 'permission denied' error depending on which template used to create database
  2023-04-18 14:08 UTC  Noah Misch <noah@leadboat.com>
  [2+ messages in thread]

BUG #17902: export/import tenant not possible due to PG internal id on jsonB fields.
  2023-04-17 11:34 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17902: export/import tenant not possible due to PG internal id on jsonB fields.
  2023-04-17 14:42 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17902: export/import tenant not possible due to PG internal id on jsonB fields.
  2023-04-17 14:57 UTC  thierry melkebeke <thierrym@gmail.com>
` Re: BUG #17902: export/import tenant not possible due to PG internal id on jsonB fields.
  2023-04-17 15:51 UTC  Greg Stark <stark@mit.edu>
` Re: BUG #17902: export/import tenant not possible due to PG internal id on jsonB fields.
  2023-04-17 16:18 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [5+ 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