pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18785: Pointer bmr.rel, dereferenced by passing as 1st parameter to function is checked for NULL later
2025-01-28 13:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18785: Pointer bmr.rel, dereferenced by passing as 1st parameter to function is checked for NULL later
2025-01-28 19:55 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #18785: Pointer bmr.rel, dereferenced by passing as 1st parameter to function is checked for NULL later
2025-01-28 20:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18785: Pointer bmr.rel, dereferenced by passing as 1st parameter to function is checked for NULL later
2025-01-28 20:12 UTC Andres Freund <andres@anarazel.de>
[4+ messages in thread]
BUG #18787: pointer te->defn not checked for NULL
2025-01-28 14:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18787: pointer te->defn not checked for NULL
2025-01-28 15:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18786: Pointer bmr.rel, dereferenced by passing as 1st parameter to function is checked for NULL later
2025-01-28 14:08 UTC PG Bug reporting form <noreply@postgresql.org>
Re: reltuples kept decreasing with each autovacuum run Re: BUG #18773: $B%*!<(B$B%H%P%-%e!<%`$N%j%H%i%$;~$K(Breltuples$B$NCM$,8:>/$9$k(B
2025-01-21 02:13 UTC $BM&<!(B $B0BF#(B <antengynnnn536@gmail.com>
` Re: reltuples kept decreasing with each autovacuum run Re: BUG #18773: $B%*!<(B$B%H%P%-%e!<%`$N%j%H%i%$;~$K(Breltuples$B$NCM$,8:>/$9$k(B
2025-01-28 07:41 UTC $B0BF#M&<!(B <antengynnnn536@gmail.com>
[2+ messages in thread]
Evidence of Ownership Issues During Restoration of Extension Member Objects
2025-01-28 05:29 UTC AKASH <akashbhujbal7051@gmail.com>
` Re: Evidence of Ownership Issues During Restoration of Extension Member Objects
2025-01-28 05:47 UTC Christophe Pettus <xof@thebuild.com>
` Re: Evidence of Ownership Issues During Restoration of Extension Member Objects
2025-01-28 05:56 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Evidence of Ownership Issues During Restoration of Extension Member Objects
2025-01-28 06:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Evidence of Ownership Issues During Restoration of Extension Member Objects
2025-01-28 06:46 UTC AKASH <akashbhujbal7051@gmail.com>
[5+ messages in thread]
PostgreSQL 17.2 servers crashing due to segmentation faults on query execution
2025-01-27 14:55 UTC Victor Castro Amigo <vcastro@AVALONINFORMATICA.COM>
` Re: PostgreSQL 17.2 servers crashing due to segmentation faults on query execution
2025-01-27 16:06 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
Superuser can't revoke role granted by non-superuser
2025-01-27 08:49 UTC Alexander Kukushkin <cyberdemn@gmail.com>
` Re: Superuser can't revoke role granted by non-superuser
2025-01-27 09:20 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Superuser can't revoke role granted by non-superuser
2025-01-27 09:22 UTC Alexander Kukushkin <cyberdemn@gmail.com>
` Re: Superuser can't revoke role granted by non-superuser
2025-01-27 09:37 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: Superuser can't revoke role granted by non-superuser
2025-01-27 10:13 UTC Alexander Kukushkin <cyberdemn@gmail.com>
` Re: Superuser can't revoke role granted by non-superuser
2025-01-27 14:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
[6+ messages in thread]
BUG #18782: Inconsistent behaviour with triggers and row level security - depends on prior number of inserts
2025-01-21 15:30 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18782: Inconsistent behaviour with triggers and row level security - depends on prior number of inserts
2025-01-25 19:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18782: Inconsistent behaviour with triggers and row level security - depends on prior number of inserts
2025-01-27 09:45 UTC Julian Wreford <julian.wreford@gearset.com>
[3+ messages in thread]
Parent index on partitioned table could still be invalid even when children are not
2025-01-23 19:09 UTC Dmytro Astapov <dastapov@gmail.com>
` Re: Parent index on partitioned table could still be invalid even when children are not
2025-01-24 12:57 UTC Dmytro Astapov <dastapov@gmail.com>
[2+ messages in thread]
BUG #18783: 2025-01-23 03:55:06.243 GMT [22929] LOG: postmaster became multithreaded 2025-01-23 03:55:06.243 GM
2025-01-23 04:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18783: 2025-01-23 03:55:06.243 GMT [22929] LOG: postmaster became multithreaded 2025-01-23 03:55:06.243 GM
2025-01-23 18:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18779: Segmentation fault while trying to connect via psql
2025-01-17 11:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18779: Segmentation fault while trying to connect via psql
2025-01-19 02:32 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: BUG #18779: Segmentation fault while trying to connect via psql
2025-01-22 08:28 UTC Даниил Элишаков <dan-eli@mail.ru>
[3+ messages in thread]
Combining array slicing and indexing causes incorrect/confusing results
2025-01-21 16:35 UTC Jelte Fennema-Nio <me@jeltef.nl>
` Re: Combining array slicing and indexing causes incorrect/confusing results
2025-01-21 17:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
回复：Re: Performance Issue when using gin index
2025-01-21 06:25 UTC 谭忠涛 <zhongtao.tan@seaboxdata.com>
Performance Issue when using gin index
2025-01-21 02:30 UTC 谭忠涛 <zhongtao.tan@seaboxdata.com>
` Re: Performance Issue when using gin index
2025-01-21 03:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18780: Bindings types are lost for complex queries
2025-01-19 22:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18780: Bindings types are lost for complex queries
2025-01-20 15:18 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18780: Bindings types are lost for complex queries
2025-01-20 15:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18780: Bindings types are lost for complex queries
2025-01-20 18:30 UTC Viktor Remennik <vik@etogo.net>
` Re: BUG #18780: Bindings types are lost for complex queries
2025-01-20 19:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18780: Bindings types are lost for complex queries
2025-01-20 21:29 UTC Viktor Remennik <vik@etogo.net>
[6+ messages in thread]
BUG #18781: pg group gy The number of returned data bars in a field is inconsistent
2025-01-20 12:52 UTC PG Bug reporting form <noreply@postgresql.org>
pg_rewind fails on Windows where tablespaces are used
2024-05-08 08:02 UTC Chris Travers <chris.travers@stormatics.tech>
` Re: pg_rewind fails on Windows where tablespaces are used
2024-06-04 04:53 UTC Michael Paquier <michael@paquier.xyz>
` Re: pg_rewind fails on Windows where tablespaces are used
2024-07-09 16:01 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: pg_rewind fails on Windows where tablespaces are used
2024-07-09 23:12 UTC Michael Paquier <michael@paquier.xyz>
` Re: pg_rewind fails on Windows where tablespaces are used
2024-07-11 01:20 UTC Chris Travers <chris.travers@stormatics.tech>
` Re: pg_rewind fails on Windows where tablespaces are used
2024-10-23 16:19 UTC Alexandra Wang <alexandra.wang.oss@gmail.com>
` Re: pg_rewind fails on Windows where tablespaces are used
2024-10-23 23:03 UTC Michael Paquier <michael@paquier.xyz>
` Re: pg_rewind fails on Windows where tablespaces are used
2024-10-28 19:00 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: pg_rewind fails on Windows where tablespaces are used
2024-10-28 23:17 UTC Michael Paquier <michael@paquier.xyz>
` Re: pg_rewind fails on Windows where tablespaces are used
2024-11-07 23:23 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: pg_rewind fails on Windows where tablespaces are used
2024-11-07 23:59 UTC Michael Paquier <michael@paquier.xyz>
` Re: pg_rewind fails on Windows where tablespaces are used
2024-11-27 01:58 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: pg_rewind fails on Windows where tablespaces are used
2024-11-27 12:52 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: pg_rewind fails on Windows where tablespaces are used
2025-01-08 14:45 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: pg_rewind fails on Windows where tablespaces are used
2025-01-09 03:38 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: pg_rewind fails on Windows where tablespaces are used
2025-01-14 21:12 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: pg_rewind fails on Windows where tablespaces are used
2025-01-18 14:37 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: pg_rewind fails on Windows where tablespaces are used
2025-01-19 01:12 UTC Michael Paquier <michael@paquier.xyz>
[18+ messages in thread]
BUG #18778: Query planning fails in ExecInitExprRec with unrecognized node type
2025-01-16 20:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18778: Query planning fails in ExecInitExprRec with unrecognized node type
2025-01-16 23:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18778: Query planning fails in ExecInitExprRec with unrecognized node type
2025-01-18 15:52 UTC Zhang Mingli <zmlpostgres@gmail.com>
` Re: BUG #18778: Query planning fails in ExecInitExprRec with unrecognized node type
2025-01-18 16:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #18777: Error running unnest function in a two phase commit transaction
2025-01-16 18:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18777: Error running unnest function in a two phase commit transaction
2025-01-16 19:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18775: PQgetCopyData always has an out-of-memory error if the table field stores bytea ~700 MB
2025-01-16 09:29 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18775: PQgetCopyData always has an out-of-memory error if the table field stores bytea ~700 MB
2025-01-16 16:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18775: PQgetCopyData always has an out-of-memory error if the table field stores bytea ~700 MB
2025-01-16 17:02 UTC Ilya Knyazev <knuazev@gmail.com>
` Re: BUG #18775: PQgetCopyData always has an out-of-memory error if the table field stores bytea ~700 MB
2025-01-16 19:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
There is a defect in the ReplicationSlotCreate() function where it iterates through ReplicationSlotCtl->replication_slots[max_replication_slots] to find a slot but does not break out of the loop when a slot is found.
2025-01-14 04:24 UTC lxiaogang5 <lxiaogang5@gmail.com>
` Re: There is a defect in the ReplicationSlotCreate() function where it iterates through ReplicationSlotCtl->replication_slots[max_replication_slots] to find a slot but does not break out of the loop when a slot is found.
2025-01-14 10:57 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: There is a defect in the ReplicationSlotCreate() function where it iterates through ReplicationSlotCtl->replication_slots[max_replication_slots] to find a slot but does not break out of the loop when a slot is found.
2025-01-14 14:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: There is a defect in the ReplicationSlotCreate() function where it iterates through ReplicationSlotCtl->replication_slots[max_replication_slots] to find a slot but does not break out of the loop when a slot is found.
2025-01-14 14:20 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: There is a defect in the ReplicationSlotCreate() function whereit iterates throughReplicationSlotCtl->replication_slots[max_replication_slots] to find a slotbut does not break out of the loop when a slot is found.
2025-01-15 02:03 UTC lxiaogang5 <lxiaogang5@gmail.com>
[5+ messages in thread]
BUG #18772: Segfaul i Greek stemming
2025-01-14 21:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18772: Segfaul i Greek stemming
2025-01-15 00:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18771: ICU custom collations with rules ignore collator strength option.
2025-01-11 17:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18771: ICU custom collations with rules ignore collator strength option.
2025-01-13 16:42 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: BUG #18771: ICU custom collations with rules ignore collator strength option.
2025-01-13 18:47 UTC Ruben Ruiz <ruben.ruizcuadrado@gmail.com>
[3+ messages in thread]
backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST
2024-11-21 15:02 UTC yuansong <yyuansong@126.com>
` Re: backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST
2024-11-21 15:58 UTC Peter Geoghegan <pg@bowt.ie>
` Re:Re: backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST
2024-11-21 21:26 UTC yuansong <yyuansong@126.com>
` Re:Re:Re: backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST
2024-11-27 10:53 UTC yuansong <yyuansong@126.com>
` Re:Re:Re:Re: backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST
2024-12-01 13:09 UTC yuansong <yyuansong@126.com>
` Re: Re:Re:Re: backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST
2024-12-01 13:33 UTC Peter Geoghegan <pg@bowt.ie>
` Re:Re: Re:Re:Re: backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST
2024-12-01 15:07 UTC yuansong <yyuansong@126.com>
` Re:Re: Re:Re:Re: backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST
2024-12-01 15:15 UTC yuansong <yyuansong@126.com>
` Re: Re: Re:Re:Re: backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST
2024-12-01 15:36 UTC Peter Geoghegan <pg@bowt.ie>
` Re:Re: Re:Re:Re: backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST
2025-01-11 09:40 UTC yuansong <yyuansong@126.com>
` Re: Re: Re:Re:Re: backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST
2025-01-12 22:43 UTC Peter Geoghegan <pg@bowt.ie>
[11+ messages in thread]
BUG #18769: ldapscheme is not displayed in pg_hba_file_rules
2025-01-09 09:45 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18769: ldapscheme is not displayed in pg_hba_file_rules
2025-01-09 09:54 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18769: ldapscheme is not displayed in pg_hba_file_rules
2025-01-09 10:00 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18769: ldapscheme is not displayed in pg_hba_file_rules
2025-01-09 12:09 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18769: ldapscheme is not displayed in pg_hba_file_rules
2025-01-10 08:00 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18769: ldapscheme is not displayed in pg_hba_file_rules
2025-01-10 08:02 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18769: ldapscheme is not displayed in pg_hba_file_rules
2025-01-12 15:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18769: ldapscheme is not displayed in pg_hba_file_rules
2025-01-12 16:20 UTC Daniel Gustafsson <daniel@yesql.se>
[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