pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18600: Getting wait_type_event as IPC:BTreePage for count queries
2024-09-04 09:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18600: Getting wait_type_event as IPC:BTreePage for count queries
2024-09-04 16:13 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #18600: Getting wait_type_event as IPC:BTreePage for count queries
2024-09-05 08:11 UTC Aditya Singh <aditya.singh@lji.io>
` Re: BUG #18600: Getting wait_type_event as IPC:BTreePage for count queries
2024-09-05 13:41 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #18600: Getting wait_type_event as IPC:BTreePage for count queries
2024-09-05 15:04 UTC Aditya Singh <aditya.singh@lji.io>
[5+ messages in thread]
BUG #18603: Yum repo does not contain 16.x version for Centos/RH/OEL7
2024-09-05 09:59 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18603: Yum repo does not contain 16.x version for Centos/RH/OEL7
2024-09-05 14:47 UTC Andrew Dunstan <andrew@dunslane.net>
[2+ messages in thread]
bug when using special caracter in password for folder.
2024-09-04 14:13 UTC François Jourdain <francois.jourdain@hotmail.com>
` Re: bug when using special caracter in password for folder.
2024-09-04 16:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: bug when using special caracter in password for folder.
2024-09-04 16:57 UTC Francois Jourdain <francois.jourdain@hotmail.com>
[3+ messages in thread]
BUG #18596: I can't download PostgreSQL16
2024-08-30 10:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18596: I can't download PostgreSQL16
2024-08-30 11:01 UTC hubert depesz lubaczewski <depesz@depesz.com>
[2+ messages in thread]
BUG #18589: pg_get_viewdef returns wrong query
2024-08-26 06:42 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18589: pg_get_viewdef returns wrong query
2024-08-26 13:07 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18589: pg_get_viewdef returns wrong query
2024-08-26 17:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18589: pg_get_viewdef returns wrong query
2024-08-27 08:46 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18589: pg_get_viewdef returns wrong query
2024-08-27 10:03 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18589: pg_get_viewdef returns wrong query
2024-08-27 13:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18589: pg_get_viewdef returns wrong query
2024-08-27 14:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18589: pg_get_viewdef returns wrong query
2024-08-28 19:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18589: pg_get_viewdef returns wrong query
2024-08-29 07:19 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18589: pg_get_viewdef returns wrong query
2024-08-29 17:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
[10+ messages in thread]
BUG #18595: Doesn't exist repodata folder in repository
2024-08-29 12:18 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18593: Container Image Vulnerabilities
2024-08-28 07:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18593: Container Image Vulnerabilities
2024-08-28 16:18 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
Postgres v16.4 crashes on segfault when memory >= 16gb
2024-08-21 19:53 UTC Weslley Braga <wbraga@implentio.com>
` Re: Postgres v16.4 crashes on segfault when memory >= 16gb
2024-08-21 21:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgres v16.4 crashes on segfault when memory >= 16gb
2024-08-27 17:20 UTC Weslley Braga <wbraga@implentio.com>
[3+ messages in thread]
Bug in PostgreSQL 15 : Facing error in PG15
2024-08-27 08:44 UTC Ram Pratap Maurya <ram.maurya@lavainternational.in>
` Re: Bug in PostgreSQL 15 : Facing error in PG15
2024-08-27 12:30 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18592: rt_raster_to_gdal: Could not load the output GDAL driver after unsuccessful paralell operation
2024-08-27 10:45 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64
2024-06-11 09:59 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64
2024-06-12 00:59 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64
2024-06-12 13:47 UTC Stefan Heine <github.stheine@heine7.de>
` Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64
2024-06-12 21:41 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64
2024-06-12 21:54 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64
2024-06-13 06:19 UTC Stefan Heine <github.stheine@heine7.de>
` Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64
2024-08-27 02:47 UTC Thomas Munro <thomas.munro@gmail.com>
[7+ messages in thread]
BUG #18590: during pg14 to pg15 migration , old passwords not migrated to scram-sha from md5
2024-08-26 08:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18590: during pg14 to pg15 migration , old passwords not migrated to scram-sha from md5
2024-08-26 13:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22 12:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22 14:34 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22 16:41 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22 17:00 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22 17:05 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22 19:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22 20:27 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22 20:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22 20:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22 21:16 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22 21:37 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22 22:44 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22 22:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22 23:11 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-22 23:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-23 01:47 UTC Andy Fan <zhihuifan1213@163.com>
` Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
2024-08-25 20:31 UTC Maxim Boguk <maxim.boguk@gmail.com>
[17+ messages in thread]
Bug or strange result of Max() on arrays containing NULL values
2024-08-24 12:54 UTC Plettenbacher, Tobias (LWF) <Tobias.Plettenbacher@lwf.bayern.de>
` Re: Bug or strange result of Max() on arrays containing NULL values
2024-08-24 14:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Bug or strange result of Max() on arrays containing NULL values
2024-08-24 15:28 UTC David G. Johnston <david.g.johnston@gmail.com>
[3+ messages in thread]
BUG #18559: Crash after detaching a partition concurrently from another session
2024-07-30 13:47 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-07-30 13:52 UTC Kuntal Ghosh <kuntalghosh.2007@gmail.com>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-07-31 02:34 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-10 13:54 UTC Junwang Zhao <zhjwpku@gmail.com>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-12 18:24 UTC Alvaro Herrera from 2ndQuadrant <alvherre@alvh.no-ip.org>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-12 22:33 UTC Alvaro Herrera from 2ndQuadrant <alvherre@alvh.no-ip.org>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-13 12:12 UTC Kuntal Ghosh <kuntalghosh.2007@gmail.com>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-13 18:18 UTC Alvaro Herrera from 2ndQuadrant <alvherre@alvh.no-ip.org>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-15 19:31 UTC Kuntal Ghosh <kuntalghosh.2007@gmail.com>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-18 14:46 UTC Junwang Zhao <zhjwpku@gmail.com>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-20 18:46 UTC Alvaro Herrera from 2ndQuadrant <alvherre@alvh.no-ip.org>
` Re: BUG #18559: Crash after detaching a partition concurrently from another session
2024-08-22 15:14 UTC Kuntal Ghosh <kuntalghosh.2007@gmail.com>
[12+ messages in thread]
BUG #18507: See C include file "ntstatus.h" for a description of the hexadecimal value.
2024-06-13 07:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18507: See C include file "ntstatus.h" for a description of the hexadecimal value.
2024-08-21 17:21 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[2+ messages in thread]
REINDEX INDEX pg_catalog.pg_default_acl_role_nsp_obj_index stuck waiting for transaction from the future in PG 13.16
2024-08-16 08:29 UTC Marcin Barczyński <mba.ogolny@gmail.com>
` Re: REINDEX INDEX pg_catalog.pg_default_acl_role_nsp_obj_index stuck waiting for transaction from the future in PG 13.16
2024-08-16 17:54 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: REINDEX INDEX pg_catalog.pg_default_acl_role_nsp_obj_index stuck waiting for transaction from the future in PG 13.16
2024-08-21 14:49 UTC Marcin Barczyński <mba.ogolny@gmail.com>
[3+ messages in thread]
CREATE CAST allows creation of binary-coercible cast to range over domain
2024-08-20 09:00 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: CREATE CAST allows creation of binary-coercible cast to range over domain
2024-08-20 14:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: CREATE CAST allows creation of binary-coercible cast to range over domain
2024-08-20 17:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: CREATE CAST allows creation of binary-coercible cast to range over domain
2024-08-21 06:14 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: CREATE CAST allows creation of binary-coercible cast to range over domain
2024-08-21 07:55 UTC Richard Guo <guofenglinux@gmail.com>
` Re: CREATE CAST allows creation of binary-coercible cast to range over domain
2024-08-21 14:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
[6+ messages in thread]
BUG #18587: PLPGSQL : conflict between variable and ON CONFLICT (a_column)
2024-08-21 12:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18587: PLPGSQL : conflict between variable and ON CONFLICT (a_column)
2024-08-21 13:17 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18587: PLPGSQL : conflict between variable and ON CONFLICT (a_column)
2024-08-21 13:30 UTC Rémi Cura <remi.cura@gmail.com>
[3+ messages in thread]
BUG #18586: Process (and transaction) is stuck in IPC when the DB is under high load
2024-08-21 11:53 UTC PG Bug reporting form <noreply@postgresql.org>
server crash on raspberry pi for large queries
2024-08-20 00:45 UTC Matthew Clark <mclark@drmatthewclark.com>
` Re: server crash on raspberry pi for large queries
2024-08-20 13:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: server crash on raspberry pi for large queries
2024-08-20 19:18 UTC Matthew Clark <mclark@drmatthewclark.com>
` Re: server crash on raspberry pi for large queries
2024-08-21 02:38 UTC David Rowley <dgrowleyml@gmail.com>
[4+ messages in thread]
FDW INSERT batching can change behavior
2024-08-09 03:07 UTC git@jasonk.me
` Re: FDW INSERT batching can change behavior
2024-08-09 19:55 UTC Tomas Vondra <tomas@vondra.me>
` Re: FDW INSERT batching can change behavior
2024-08-13 04:57 UTC Jason Kim <git@jasonk.me>
` Re: FDW INSERT batching can change behavior
2024-08-13 12:12 UTC Tomas Vondra <tomas@vondra.me>
` Re: FDW INSERT batching can change behavior
2024-08-13 18:31 UTC Tomas Vondra <tomas@vondra.me>
` Re: FDW INSERT batching can change behavior
2024-08-14 11:31 UTC Tomas Vondra <tomas@vondra.me>
` Re: FDW INSERT batching can change behavior
2024-08-20 21:47 UTC Tomas Vondra <tomas@vondra.me>
[7+ messages in thread]
BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-07 15:48 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-08 10:44 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-08 17:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-08 20:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-09 03:25 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-09 03:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-09 15:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-19 11:23 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-19 16:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-19 17:11 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-19 17:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-19 19:16 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18576: Using EXPLAIN (VERBOSE) in information_schema.element_types returns ERROR: failed to find plan for
2024-08-20 09:43 UTC Andrei Lepikhov <lepihov@gmail.com>
[13+ messages in thread]
Report Postgres Bug - Unlogged table sequence
2024-08-19 05:47 UTC Sindhu S <sindhusanti@gmail.com>
` Re: Report Postgres Bug - Unlogged table sequence
2024-08-19 08:57 UTC Aleksander Alekseev <aleksander@timescale.com>
` Re: Report Postgres Bug - Unlogged table sequence
2024-08-19 13:41 UTC Zaid Shabbir <zaidshabbir@gmail.com>
` Re: Report Postgres Bug - Unlogged table sequence
2024-08-20 03:37 UTC Sindhu S <sindhusanti@gmail.com>
[4+ messages in thread]
Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
2024-07-22 14:46 UTC Mohammed Siddiqui <msiddiqui@net32.com>
` Re: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
2024-07-23 08:33 UTC Aleksander Alekseev <aleksander@timescale.com>
` RE: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
2024-07-25 03:51 UTC Mohammed Siddiqui <msiddiqui@net32.com>
` Re: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
2024-07-30 12:36 UTC Muhammad Waqas <waqas.m@bitnine.net>
` Re: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
2024-07-30 13:15 UTC Zaid Shabbir <zaidshabbir@gmail.com>
` RE: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
2024-07-30 13:34 UTC Mohammed Siddiqui <msiddiqui@net32.com>
` Re: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
2024-07-30 13:41 UTC Zaid Shabbir <zaidshabbir@gmail.com>
` Re: Intermittent aggressive use of SWAP space by PostgreSQL despite availability of HUGE amounts of RAM for a small database.
2024-08-19 17:20 UTC Bruce Momjian <bruce@momjian.us>
[8+ 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