pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17725: Sefault when seg_in() called with a large argument
2022-12-20 03:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17725: Sefault when seg_in() called with a large argument
2022-12-20 10:13 UTC John Naylor <john.naylor@enterprisedb.com>
` Re: BUG #17725: Sefault when seg_in() called with a large argument
2022-12-20 12:48 UTC Robins Tharakan <tharakan@gmail.com>
` Re: BUG #17725: Sefault when seg_in() called with a large argument
2022-12-20 16:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17725: Sefault when seg_in() called with a large argument
2022-12-20 17:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #17713: Assert with postgres_fdw in v12
2022-12-12 04:12 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17713: Assert with postgres_fdw in v12
2022-12-13 03:20 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17713: Assert with postgres_fdw in v12
2022-12-14 10:02 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #17713: Assert with postgres_fdw in v12
2022-12-15 12:33 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #17713: Assert with postgres_fdw in v12
2022-12-19 12:03 UTC Robins Tharakan <tharakan@gmail.com>
[5+ messages in thread]
BUG #17724: All autovacuum workers operate on 1 db at a time
2022-12-16 17:52 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17724: All autovacuum workers operate on 1 db at a time
2022-12-16 21:26 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #17723: cache lookup failed for type 0
2022-12-16 15:38 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17723: cache lookup failed for type 0
2022-12-16 17:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17723: cache lookup failed for type 0
2022-12-16 19:36 UTC Vik Fearing <vik@postgresfriends.org>
[3+ messages in thread]
pg_rewind succeed but postgresql showing error when trying to make standby with common ancestor
2022-12-15 09:33 UTC niraj nandane <niraj.nandane@gmail.com>
` Re: pg_rewind succeed but postgresql showing error when trying to make standby with common ancestor
2022-12-16 02:11 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: pg_rewind succeed but postgresql showing error when trying to make standby with common ancestor
2022-12-16 06:03 UTC niraj nandane <niraj.nandane@gmail.com>
[3+ messages in thread]
BUG #17710: Slow queries (100% CPU) after auto-vacuum
2022-12-09 15:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17710: Slow queries (100% CPU) after auto-vacuum
2022-12-10 02:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17710: Slow queries (100% CPU) after auto-vacuum
2022-12-12 14:37 UTC Jean-Francois Levesque <jf.levesque@gmail.com>
` Re: BUG #17710: Slow queries (100% CPU) after auto-vacuum
2022-12-12 18:36 UTC Jean-Francois Levesque <jf.levesque@gmail.com>
` Re: BUG #17710: Slow queries (100% CPU) after auto-vacuum
2022-12-13 01:40 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17710: Slow queries (100% CPU) after auto-vacuum
2022-12-13 01:46 UTC Jean-Francois Levesque <jf.levesque@gmail.com>
` Re: BUG #17710: Slow queries (100% CPU) after auto-vacuum
2022-12-13 02:39 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17710: Slow queries (100% CPU) after auto-vacuum
2022-12-15 20:41 UTC Jean-Francois Levesque <jf.levesque@gmail.com>
[8+ messages in thread]
BUG #17721: A completely unused CTE negatively affect Query Plan
2022-12-14 17:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17721: A completely unused CTE negatively affect Query Plan
2022-12-14 18:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17721: A completely unused CTE negatively affect Query Plan
2022-12-14 22:14 UTC Nathaniel Hazelton <nathaniel@sturdyai.com>
` Re: BUG #17721: A completely unused CTE negatively affect Query Plan
2022-12-14 22:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17721: A completely unused CTE negatively affect Query Plan
2022-12-15 05:45 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17721: A completely unused CTE negatively affect Query Plan
2022-12-15 16:23 UTC Nathaniel Hazelton <nathaniel@sturdyai.com>
[6+ messages in thread]
Sort bug
2022-12-14 07:20 UTC okijhhyu <okijhhyu@gmail.com>
` Re: Sort bug
2022-12-14 10:22 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Sort bug
2022-12-14 10:28 UTC Pavel Borisov <pashkin.elfe@gmail.com>
[3+ messages in thread]
BUG #17719: scram-sha-256 is not working on PostgreSQL 11.18
2022-12-13 21:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17719: scram-sha-256 is not working on PostgreSQL 11.18
2022-12-14 02:56 UTC Michael Paquier <michael@paquier.xyz>
[2+ messages in thread]
BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-03-11 11:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-14 23:49 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-15 00:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-15 02:14 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-15 21:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-18 19:55 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-18 20:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-18 22:17 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-19 11:16 UTC Daniel Verite <daniel@manitou-mail.org>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-26 15:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-26 15:22 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-26 15:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-26 15:48 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-26 16:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-26 16:11 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-26 16:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-28 01:51 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-28 02:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-07-28 16:13 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-08-08 15:21 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-09-30 01:23 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-11-06 17:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-11-09 10:01 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-11-09 16:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-11-09 16:24 UTC Peter Eisentraut <peter.eisentraut@enterprisedb.com>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-11-09 16:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-11-10 04:49 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-11-10 05:48 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-11-10 20:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-11-16 10:53 UTC Yugo NAGATA <nagata@sraoss.co.jp>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-11-25 15:17 UTC Israel Barth Rubio <barthisrael@gmail.com>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-11-25 17:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-12-12 19:16 UTC Peter Eisentraut <peter.eisentraut@enterprisedb.com>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-12-12 21:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
2022-12-13 19:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
[35+ messages in thread]
BUG #17718: Unexpected REVOKE ALL permissions in the backup script
2022-12-13 18:59 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17706: ALTER TYPE leads to crash
2022-12-07 20:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17706: ALTER TYPE leads to crash
2022-12-08 04:16 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17706: ALTER TYPE leads to crash
2022-12-08 05:01 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17706: ALTER TYPE leads to crash
2022-12-13 02:58 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17706: ALTER TYPE leads to crash
2022-12-13 03:45 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17706: ALTER TYPE leads to crash
2022-12-13 06:58 UTC Sergey Shinderuk <s.shinderuk@postgrespro.ru>
[6+ messages in thread]
jsonb subscript operator returns null when key is fetched from table
2022-12-09 20:06 UTC exe-dealer <exe-dealer@yandex.ru>
` Re: jsonb subscript operator returns null when key is fetched from table
2022-12-12 18:51 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: jsonb subscript operator returns null when key is fetched from table
2022-12-12 19:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #17714: Refresh materialized view does not update all date
2022-12-12 10:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17714: Refresh materialized view does not update all date
2022-12-12 17:03 UTC Jeff Davis <pgsql@j-davis.com>
[2+ messages in thread]
BUG #17715: dumps file raise an error on restore if a materialized view use a function calling another function
2022-12-12 15:42 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17715: dumps file raise an error on restore if a materialized view use a function calling another function
2022-12-12 16:38 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #17711: Login failed
2022-12-11 13:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17711: Login failed
2022-12-11 15:29 UTC Jeff Janes <jeff.janes@gmail.com>
[2+ messages in thread]
BUG #17709: Regression in PG15 with window functions - "WindowFunc not found in subplan target lists"
2022-12-09 08:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17709: Regression in PG15 with window functions - "WindowFunc not found in subplan target lists"
2022-12-09 11:00 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17709: Regression in PG15 with window functions - "WindowFunc not found in subplan target lists"
2022-12-09 11:52 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17709: Regression in PG15 with window functions - "WindowFunc not found in subplan target lists"
2022-12-09 14:01 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17709: Regression in PG15 with window functions - "WindowFunc not found in subplan target lists"
2022-12-10 06:29 UTC David Rowley <dgrowleyml@gmail.com>
[5+ messages in thread]
BUG #17708: 12.4
2022-12-09 05:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17708: 12.4
2022-12-09 14:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
CREATE COLLATION without LOCALE throws error in v15
2022-12-02 19:14 UTC Kyle Spearrin <kspearrin@bitwarden.com>
` Re: CREATE COLLATION without LOCALE throws error in v15
2022-12-06 23:57 UTC Jeff Davis <pgsql@j-davis.com>
` Re: CREATE COLLATION without LOCALE throws error in v15
2022-12-07 12:04 UTC Peter Eisentraut <peter.eisentraut@enterprisedb.com>
` Re: CREATE COLLATION without LOCALE throws error in v15
2022-12-07 17:44 UTC Jeff Davis <pgsql@j-davis.com>
` Re: CREATE COLLATION without LOCALE throws error in v15
2022-12-08 18:29 UTC Peter Eisentraut <peter.eisentraut@enterprisedb.com>
` Re: CREATE COLLATION without LOCALE throws error in v15
2022-12-08 19:59 UTC Jeff Davis <pgsql@j-davis.com>
` Re: CREATE COLLATION without LOCALE throws error in v15
2022-12-08 20:02 UTC Kyle Spearrin <kspearrin@bitwarden.com>
` Re: CREATE COLLATION without LOCALE throws error in v15
2022-12-08 20:03 UTC Justin Baur <jbaur@bitwarden.com>
[8+ messages in thread]
BUG #17707: Foreign key verification is very slow while creating empty partitions
2022-12-08 08:41 UTC PG Bug reporting form <noreply@postgresql.org>
Re[4]: PG 14.5 -- Impossible to restore dump due to interaction/order of views, functions, and generated columns
2022-12-07 15:28 UTC Nunya Business <nb3425586@gmail.com>
Re[2]: PG 14.5 -- Impossible to restore dump due to interaction/order of views, functions, and generated columns
2022-12-06 18:19 UTC Nunya Business <nb3425586@gmail.com>
` Re: Re[2]: PG 14.5 -- Impossible to restore dump due to interaction/order of views, functions, and generated columns
2022-12-06 20:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
PG 14.5 -- Impossible to restore dump due to interaction/order of views, functions, and generated columns
2022-12-05 19:49 UTC Nunya Business <nb3425586@gmail.com>
` Re: PG 14.5 -- Impossible to restore dump due to interaction/order of views, functions, and generated columns
2022-12-06 15:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: PG 14.5 -- Impossible to restore dump due to interaction/order of views, functions, and generated columns
2022-12-06 15:51 UTC Adrian Klaver <adrian.klaver@aklaver.com>
[3+ messages in thread]
BUG #17705: Segmentation fault in BufFileLoadBuffer
2022-12-03 21:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17705: Segmentation fault in BufFileLoadBuffer
2022-12-05 03:40 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #17705: Segmentation fault in BufFileLoadBuffer
2022-12-05 06:24 UTC Vahur Sinijärv <vahursi@icloud.com>
` Re: BUG #17705: Segmentation fault in BufFileLoadBuffer
2022-12-05 10:09 UTC Thomas Munro <thomas.munro@gmail.com>
[4+ messages in thread]
hashing bpchar for nondeterministic collations is broken
2022-12-01 20:11 UTC Jeff Davis <pgsql@j-davis.com>
` Re: hashing bpchar for nondeterministic collations is broken
2022-12-02 02:30 UTC Richard Guo <guofenglinux@gmail.com>
` Re: hashing bpchar for nondeterministic collations is broken
2022-12-02 20:05 UTC Jeff Davis <pgsql@j-davis.com>
` Re: hashing bpchar for nondeterministic collations is broken
2022-12-02 21:21 UTC Jeff Davis <pgsql@j-davis.com>
` Re: hashing bpchar for nondeterministic collations is broken
2022-12-02 21:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: hashing bpchar for nondeterministic collations is broken
2022-12-02 22:04 UTC Jeff Davis <pgsql@j-davis.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