pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedperformance: `tuplehash_iterate` and `group by` question, very slow
2024-03-20 09:55 UTC Mingjun Yang <yangxiaoming2019@gmail.com>
BUG #18399: Query plan optimization results in runtime error when hoisting cast from inside subquery
2024-03-18 23:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18399: Query plan optimization results in runtime error when hoisting cast from inside subquery
2024-03-19 15:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18399: Query plan optimization results in runtime error when hoisting cast from inside subquery
2024-03-19 23:11 UTC Sawyer Knoblich <scknoblich@gmail.com>
` Re: BUG #18399: Query plan optimization results in runtime error when hoisting cast from inside subquery
2024-03-20 00:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18399: Query plan optimization results in runtime error when hoisting cast from inside subquery
2024-03-20 02:20 UTC Sawyer Knoblich <scknoblich@gmail.com>
` Re: BUG #18399: Query plan optimization results in runtime error when hoisting cast from inside subquery
2024-03-20 04:08 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18399: Query plan optimization results in runtime error when hoisting cast from inside subquery
2024-03-20 04:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18399: Query plan optimization results in runtime error when hoisting cast from inside subquery
2024-03-20 06:37 UTC Sawyer Knoblich <scknoblich@gmail.com>
[8+ messages in thread]
BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update
2024-03-14 03:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update
2024-03-14 05:58 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update
2024-03-14 06:03 UTC Carl Smith <carl@msupply.foundation>
` Re: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update
2024-03-14 08:55 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update
2024-03-14 21:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18392: Can't restore database (using pg_restore) after latest Feb 8 update
2024-03-19 23:57 UTC Carl Smith <carl@msupply.foundation>
[6+ messages in thread]
Postgres jdbc driver inconsistent behaviour with double precession
2024-03-16 17:55 UTC Rahul Uniyal <rahul.uniyal00@gmail.com>
` Re: Postgres jdbc driver inconsistent behaviour with double precession
2024-03-18 20:18 UTC Dave Cramer <davecramer@postgres.rocks>
` Re: Postgres jdbc driver inconsistent behaviour with double precession
2024-03-18 21:33 UTC Rahul Uniyal <rahul.uniyal00@gmail.com>
` Re: Postgres jdbc driver inconsistent behaviour with double precession
2024-03-18 22:36 UTC Dave Cramer <davecramer@postgres.rocks>
` Re: Postgres jdbc driver inconsistent behaviour with double precession
2024-03-19 09:52 UTC Dave Cramer <davecramer@postgres.rocks>
` Re: Postgres jdbc driver inconsistent behaviour with double precession
2024-03-19 11:39 UTC Dave Cramer <davecramer@postgres.rocks>
` Re: Postgres jdbc driver inconsistent behaviour with double precession
2024-03-19 18:15 UTC Rahul Uniyal <rahul.uniyal00@gmail.com>
[7+ messages in thread]
BUG #18400: logging_collector does not collect messages from postmaster
2024-03-19 15:31 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18398: Simplified SQL Query for Problem Diagnosis
2024-03-18 14:05 UTC PG Bug reporting form <noreply@postgresql.org>
PostgreSQL & latest Mac OS Sonoma, a possible bug / configuration issue
2024-02-05 19:03 UTC Arnd Baranowski <baranowski@oculeus.com>
` Re: PostgreSQL & latest Mac OS Sonoma, a possible bug / configuration issue
2024-02-05 20:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL & latest Mac OS Sonoma, a possible bug / configuration issue
2024-02-05 22:00 UTC Arnd Baranowski <baranowski@oculeus.com>
` Re: PostgreSQL & latest Mac OS Sonoma, a possible bug / configuration issue
2024-02-05 22:10 UTC Arnd Baranowski <baranowski@oculeus.com>
` Re: PostgreSQL & latest Mac OS Sonoma, a possible bug / configuration issue
2024-02-06 02:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL & latest Mac OS Sonoma, a possible bug / configuration issue
2024-02-06 08:07 UTC Arnd Baranowski <baranowski@oculeus.com>
` Re: PostgreSQL & latest Mac OS Sonoma, a possible bug / configuration issue
2024-03-15 09:54 UTC Arnd Baranowski <baranowski@oculeus.com>
[7+ messages in thread]
BUG #18385: Assert("strategy_delta >= 0") in BgBufferSync() fails due to race condition
2024-03-10 19:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18385: Assert("strategy_delta >= 0") in BgBufferSync() fails due to race condition
2024-03-13 06:50 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18385: Assert("strategy_delta >= 0") in BgBufferSync() fails due to race condition
2024-03-13 08:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18385: Assert("strategy_delta >= 0") in BgBufferSync() fails due to race condition
2024-03-15 08:05 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18385: Assert("strategy_delta >= 0") in BgBufferSync() fails due to race condition
2024-03-15 08:48 UTC Tender Wang <tndrwang@gmail.com>
[5+ messages in thread]
BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view
2024-03-11 20:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view
2024-03-11 23:02 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view
2024-03-11 23:21 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view
2024-03-12 07:34 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view
2024-03-12 10:40 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view
2024-03-12 12:22 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view
2024-03-12 13:51 UTC Wetmore, Matthew (CTR) <Matthew.Wetmore@evernorth.com>
` Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view
2024-03-12 14:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view
2024-03-13 17:08 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view
2024-03-13 18:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18387: Erroneous permission checks and/or misleading error messages with refresh materialized view
2024-03-15 02:36 UTC Bruce Momjian <bruce@momjian.us>
[11+ messages in thread]
BUG #18394: LISTEN error: could not access status of transaction
2024-03-14 22:00 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18393: Bad multiple "inplace" insert into domain of complex type
2024-03-14 06:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18393: Bad multiple "inplace" insert into domain of complex type
2024-03-14 15:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18390: exponentiation produces float datatype, but nth-root produces integer
2024-03-13 02:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18390: exponentiation produces float datatype, but nth-root produces integer
2024-03-13 12:07 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18390: exponentiation produces float datatype, but nth-root produces integer
2024-03-13 14:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
AW: BUG #18389: pg_database_owner not recognized with alter default privileges
2024-03-13 07:16 UTC Kristo Marijo <M.Kristo@rewe-group.at>
` AW: BUG #18389: pg_database_owner not recognized with alter default privileges
2024-03-13 09:22 UTC Kristo Marijo <M.Kristo@rewe-group.at>
[2+ messages in thread]
BUG #18389: pg_database_owner not recognized with alter default privileges
2024-03-12 19:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18389: pg_database_owner not recognized with alter default privileges
2024-03-12 19:55 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #18389: pg_database_owner not recognized with alter default privileges
2024-03-13 08:44 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18389: pg_database_owner not recognized with alter default privileges
2024-03-13 08:47 UTC Kristo Marijo <M.Kristo@rewe-group.at>
` Re: BUG #18389: pg_database_owner not recognized with alter default privileges
2024-03-13 09:07 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[5+ messages in thread]
A server crash with a SQL procedure returning a user-defined type on 14.8
2024-03-11 22:19 UTC Yahor Yuzefovich <yahor@cockroachlabs.com>
` Re: A server crash with a SQL procedure returning a user-defined type on 14.8
2024-03-12 19:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-02-16 13:18 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-02-16 14:40 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-02-20 14:05 UTC Alexey Ermakov <alexey.ermakov@dataegret.com>
` Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-02-21 12:52 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-02-29 03:36 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-03-01 09:50 UTC Alexey Ermakov <alexey.ermakov@dataegret.com>
` Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-03-01 12:48 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-03-01 15:54 UTC Alexey Ermakov <alexey.ermakov@dataegret.com>
` Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-03-03 22:12 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-03-03 23:49 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-03-04 00:11 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-03-04 00:20 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-03-11 08:12 UTC Alexey Ermakov <alexey.ermakov@dataegret.com>
` Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-03-12 06:44 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
[14+ messages in thread]
BUG #18388: Server freezes after AuthenticationSASLFinal message
2024-03-11 22:13 UTC PG Bug reporting form <noreply@postgresql.org>
"type with xxxx does not exist" when doing ExecMemoize()
2024-02-25 13:32 UTC Tender Wang <tndrwang@gmail.com>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-02-26 02:52 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-02-26 05:38 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-02-26 07:54 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-02-26 08:14 UTC Tender Wang <tndrwang@gmail.com>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-02-26 09:30 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-02-26 11:34 UTC Richard Guo <guofenglinux@gmail.com>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-02-26 12:29 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-02-28 06:53 UTC Tender Wang <tndrwang@gmail.com>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-02-28 07:25 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-02-29 05:25 UTC Tender Wang <tndrwang@gmail.com>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-03-01 07:18 UTC Tender Wang <tndrwang@gmail.com>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-03-05 09:36 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-03-06 03:10 UTC Tender Wang <tndrwang@gmail.com>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-03-06 03:37 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-03-07 02:24 UTC Tender Wang <tndrwang@gmail.com>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-03-07 09:50 UTC David Rowley <dgrowleyml@gmail.com>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-03-11 05:25 UTC David Rowley <dgrowleyml@gmail.com>
` Re: "type with xxxx does not exist" when doing ExecMemoize()
2024-03-11 05:31 UTC Tender Wang <tndrwang@gmail.com>
[19+ messages in thread]
RE:Undetected deadlock between client backend and startup processes on a standby (Previously, Undetected deadlock between primary and standby processes)
2024-03-04 08:35 UTC Rintaro.Ikeda@nttdata.com
` Re: Undetected deadlock between client backend and startup processes on a standby (Previously, Undetected deadlock between primary and standby processes)
2024-03-10 20:43 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
[2+ messages in thread]
BUG #18384: It's not bug just question about documentation
2024-03-08 06:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18384: It's not bug just question about documentation
2024-03-08 15:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
facing an issue with the installation of pljava 1.6.6.
2024-03-08 09:55 UTC Shankarigari Ashok <ashok.shankarigari@aaseya.com>
BUG #18383: creation of public schema is not consistent
2024-03-07 17:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18383: creation of public schema is not consistent
2024-03-07 19:47 UTC Sam Darwin <samuel.d.darwin@gmail.com>
` Re: BUG #18383: creation of public schema is not consistent
2024-03-07 20:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18383: creation of public schema is not consistent
2024-03-08 01:48 UTC Sam Darwin <samuel.d.darwin@gmail.com>
` Re: BUG #18383: creation of public schema is not consistent
2024-03-08 07:31 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[5+ messages in thread]
BUG #18212: Functions txid_status() and pg_xact_status() return invalid status of the specified transaction
2023-11-24 06:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18212: Functions txid_status() and pg_xact_status() return invalid status of the specified transaction
2023-11-24 11:38 UTC Karina Litskevich <litskevichkarina@gmail.com>
` Re: BUG #18212: Functions txid_status() and pg_xact_status() return invalid status of the specified transaction
2023-11-28 05:20 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #18212: Functions txid_status() and pg_xact_status() return invalid status of the specified transaction
2023-11-30 05:30 UTC Karina Litskevich <litskevichkarina@gmail.com>
` Re: BUG #18212: Functions txid_status() and pg_xact_status() return invalid status of the specified transaction
2024-02-05 13:51 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18212: Functions txid_status() and pg_xact_status() return invalid status of the specified transaction
2024-02-05 14:35 UTC Karina Litskevich <litskevichkarina@gmail.com>
` Re: BUG #18212: Functions txid_status() and pg_xact_status() return invalid status of the specified transaction
2024-02-05 14:50 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18212: Functions txid_status() and pg_xact_status() return invalid status of the specified transaction
2024-02-06 12:58 UTC Karina Litskevich <litskevichkarina@gmail.com>
` Re: BUG #18212: Functions txid_status() and pg_xact_status() return invalid status of the specified transaction
2024-03-07 13:17 UTC Maxim Orlov <orlovmg@gmail.com>
` Re: BUG #18212: Functions txid_status() and pg_xact_status() return invalid status of the specified transaction
2024-03-07 13:34 UTC Alexander Korotkov <aekorotkov@gmail.com>
[10+ messages in thread]
BUG #18381: Invalid query generated by postgres_fdw with UNION ALL and ORDER BY
2024-03-07 10:22 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18381: Invalid query generated by postgres_fdw with UNION ALL and ORDER BY
2024-03-07 11:32 UTC David Rowley <dgrowleyml@gmail.com>
[2+ messages in thread]
[PATCH v2] Detect FSM corruption and repair it.
2024-03-07 08:40 UTC Ronan Dunklau <ronan.dunklau@aiven.io>
` [PATCH v3] Detect FSM corruption and repair it.
2024-03-07 08:40 UTC Ronan Dunklau <ronan.dunklau@aiven.io>
[2+ 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