pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18879: PostgreSQL returns memory error.
2025-04-04 19:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18879: PostgreSQL returns memory error.
2025-04-04 21:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2024-03-17 07:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2024-03-19 12:07 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2024-03-19 14:26 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2024-03-20 05:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2024-03-20 06:22 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2024-03-26 12:09 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2024-11-15 09:10 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2025-04-04 11:04 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18396: Assert in gistFindCorrectParent() fails on inserting large tuples into gist index
2025-04-04 20:00 UTC Alexander Lakhin <exclusion@gmail.com>
[9+ messages in thread]
BUG #18875: COPY BINARY tsvector FROM file leads to misaligned memory access
2025-04-02 19:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18875: COPY BINARY tsvector FROM file leads to misaligned memory access
2025-04-02 19:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17821: Assertion failed in heap_update() due to heap pruning
2023-03-02 13:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2023-03-04 06:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2023-03-04 16:48 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2023-10-07 08:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2024-04-09 12:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2024-04-09 17:41 UTC Melanie Plageman <melanieplageman@gmail.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2024-04-09 19:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2024-11-13 00:26 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2025-01-11 21:44 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2025-01-23 02:13 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2025-03-03 22:07 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2025-03-04 03:34 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #17821: Assertion failed in heap_update() due to heap pruning
2025-04-02 17:04 UTC Noah Misch <noah@leadboat.com>
[13+ messages in thread]
BUG #18874: CVE-2024-4317
2025-04-01 14:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18874: CVE-2024-4317
2025-04-01 14:43 UTC Álvaro Herrera <alvherre@alvh.no-ip.org>
[2+ messages in thread]
Summing of INTERVAL returns incorrect number of days and hours
2025-04-01 13:13 UTC Milan Novotny <xnovm149@gmail.com>
` Re: Summing of INTERVAL returns incorrect number of days and hours
2025-04-01 14:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Download Issue
2025-03-31 20:01 UTC farida yasmeen <faridayasmeencse@gmail.com>
` Re: Download Issue
2025-03-31 21:01 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
PostgreSQL 17.4 bug with JSON+UUID under high load
2025-03-31 08:38 UTC Constantine Plotnikov <constantine.plotnikov@gmail.com>
PostgreSQL JDBC 42.7.5 returns an unexpected catalog name
2025-03-28 18:24 UTC Vinhson Nguyen <Vinhson.Nguyen@ca.ibm.com>
` Fwd: PostgreSQL JDBC 42.7.5 returns an unexpected catalog name
2025-03-29 16:21 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: PostgreSQL JDBC 42.7.5 returns an unexpected catalog name
2025-03-29 18:53 UTC Andrew Dunstan <andrew@dunslane.net>
[3+ messages in thread]
BUG #18871: Cross-partition MERGE fails with unclear internal error
2025-03-28 05:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18871: Cross-partition MERGE fails with unclear internal error
2025-03-28 16:39 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18871: Cross-partition MERGE fails with unclear internal error
2025-03-28 18:29 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #18871: Cross-partition MERGE fails with unclear internal error
2025-03-29 02:39 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18871: Cross-partition MERGE fails with unclear internal error
2025-03-29 05:54 UTC Gurjeet Singh <gurjeet@singh.im>
` Re: BUG #18871: Cross-partition MERGE fails with unclear internal error
2025-03-29 10:20 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #18871: Cross-partition MERGE fails with unclear internal error
2025-03-29 10:40 UTC Tender Wang <tndrwang@gmail.com>
[7+ messages in thread]
BUG #18832: Segfault in GrantLockLocal
2025-03-06 01:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18832: Segfault in GrantLockLocal
2025-03-07 00:49 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18832: Segfault in GrantLockLocal
2025-03-07 10:37 UTC Álvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18832: Segfault in GrantLockLocal
2025-03-27 09:42 UTC Robins Tharakan <tharakan@gmail.com>
` Re: BUG #18832: Segfault in GrantLockLocal
2025-03-28 06:00 UTC Alexander Lakhin <exclusion@gmail.com>
[5+ messages in thread]
BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-25 14:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-25 15:45 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-25 16:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-26 01:18 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-26 01:55 UTC Euler Taveira <euler@eulerto.com>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-26 16:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-26 16:51 UTC Euler Taveira <euler@eulerto.com>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-26 17:33 UTC Álvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-26 19:00 UTC Euler Taveira <euler@eulerto.com>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-26 19:06 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-27 07:14 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-27 08:48 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-27 16:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18866: Running pg_freespace() on views triggers an Abort
2025-03-28 01:59 UTC Tender Wang <tndrwang@gmail.com>
[14+ messages in thread]
BUG #18856: Include directives for postgresql.conf, pg_hba.conf, pg_ident.conf behave inconsistently.
2025-03-18 22:30 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18856: Include directives for postgresql.conf, pg_hba.conf, pg_ident.conf behave inconsistently.
2025-03-18 22:38 UTC Robert Pufky <rpufky@gmail.com>
` Re: BUG #18856: Include directives for postgresql.conf, pg_hba.conf, pg_ident.conf behave inconsistently.
2025-03-28 01:24 UTC Michael Paquier <michael@paquier.xyz>
[3+ messages in thread]
BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-14 07:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-14 13:50 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-14 14:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-14 14:08 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-14 22:10 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-15 17:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-16 19:59 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-16 20:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-17 08:26 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL
2025-03-27 22:49 UTC Daniel Gustafsson <daniel@yesql.se>
[10+ messages in thread]
BUG #18870: weird behavior with regexp_replace
2025-03-27 13:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18870: weird behavior with regexp_replace
2025-03-27 21:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18855: Using BRIN index with int8_bloom_ops produces incorrect results
2025-03-18 20:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18855: Using BRIN index with int8_bloom_ops produces incorrect results
2025-03-19 13:43 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #18855: Using BRIN index with int8_bloom_ops produces incorrect results
2025-03-19 17:11 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #18855: Using BRIN index with int8_bloom_ops produces incorrect results
2025-03-19 19:53 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #18855: Using BRIN index with int8_bloom_ops produces incorrect results
2025-03-26 16:09 UTC Tomas Vondra <tomas@vondra.me>
[5+ messages in thread]
BUG #18869: /src/backend/optimizer/plan/createplan.c clause can be null if user isn't root
2025-03-26 10:20 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18869: /src/backend/optimizer/plan/createplan.c clause can be null if user isn't root
2025-03-26 14:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18868: /src/backend/optimizer/path/joinrels.c list_head can be NULL
2025-03-26 10:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18868: /src/backend/optimizer/path/joinrels.c list_head can be NULL
2025-03-26 14:27 UTC Euler Taveira <euler@eulerto.com>
[2+ messages in thread]
BUG #18867: /src/interfaces/ecpg/preproc/descriptor.c usage of ECPGdump_a_type
2025-03-26 10:13 UTC PG Bug reporting form <noreply@postgresql.org>
ltree gist index "incomplete split"
2025-03-25 22:05 UTC Wyatt Berlinic <wyatt@peregrine.io>
BUG #18865: pg_resetwal error: multitransaction offset (-O) must not be -1
2025-03-25 10:08 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18861: Not able to download rpm package
2025-03-21 10:52 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18861: Not able to download rpm package
2025-03-25 07:53 UTC Devrim Gündüz <devrim@gunduz.org>
` Re: BUG #18861: Not able to download rpm package
2025-03-25 07:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #18862: using pg_autoctl node_2 cannot bring back from maintenance mode
2025-03-24 15:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18862: using pg_autoctl node_2 cannot bring back from maintenance mode
2025-03-25 07:54 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #18863: Multixact wraparound and pg_resetwal error "multitransaction ID (-m) must not be 0"
2025-03-24 18:35 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18859: ERROR: unexpected plan node type: 356
2025-03-20 13:53 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18859: ERROR: unexpected plan node type: 356
2025-03-21 12:58 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18859: ERROR: unexpected plan node type: 356
2025-03-21 13:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18859: ERROR: unexpected plan node type: 356
2025-03-21 14:49 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18859: ERROR: unexpected plan node type: 356
2025-03-21 15:09 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18859: ERROR: unexpected plan node type: 356
2025-03-21 15:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18859: ERROR: unexpected plan node type: 356
2025-03-21 15:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
[7+ 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