pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #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]
BUG #18770: The function 'packGraph ' causes a memory leak.
2025-01-10 01:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18770: The function 'packGraph ' causes a memory leak.
2025-01-10 14:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18663: synchronous_standby_names vs synchronous_commit vs pg_stat_replication
2024-10-18 14:48 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18663: synchronous_standby_names vs synchronous_commit vs pg_stat_replication
2024-10-21 09:43 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #18663: synchronous_standby_names vs synchronous_commit vs pg_stat_replication
2025-01-09 00:35 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #18663: synchronous_standby_names vs synchronous_commit vs pg_stat_replication
2025-01-09 12:11 UTC Fujii Masao <masao.fujii@oss.nttdata.com>
` Re: BUG #18663: synchronous_standby_names vs synchronous_commit vs pg_stat_replication
2025-01-10 11:54 UTC Asphator <asphator@gmail.com>
[5+ messages in thread]
BUG #18764: server closed the connection unexpectedly
2025-01-03 07:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18764: server closed the connection unexpectedly
2025-01-03 16:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18764: server closed the connection unexpectedly
2025-01-03 17:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18764: server closed the connection unexpectedly
2025-01-06 13:14 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18764: server closed the connection unexpectedly
2025-01-07 07:00 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18764: server closed the connection unexpectedly
2025-01-09 03:30 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18764: server closed the connection unexpectedly
2025-01-09 03:44 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18764: server closed the connection unexpectedly
2025-01-09 03:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18764: server closed the connection unexpectedly
2025-01-09 04:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18764: server closed the connection unexpectedly
2025-01-09 07:38 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18764: server closed the connection unexpectedly
2025-01-10 01:35 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18764: server closed the connection unexpectedly
2025-01-10 02:41 UTC dqetool <dqetool@126.com>
[12+ messages in thread]
BUG #18765: Inconsistent behaviour and errors with LIKE
2025-01-03 16:47 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18765: Inconsistent behaviour and errors with LIKE
2025-01-03 17:21 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18765: Inconsistent behaviour and errors with LIKE
2025-01-06 19:07 UTC Anmol Mohanty <anmol.mohanty@salesforce.com>
` Re: BUG #18765: Inconsistent behaviour and errors with LIKE
2025-01-06 19:25 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18765: Inconsistent behaviour and errors with LIKE
2025-01-08 20:52 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: BUG #18765: Inconsistent behaviour and errors with LIKE
2025-01-08 21:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
[6+ messages in thread]
Incorrect result in certain expressions of anti-join
2025-01-07 17:51 UTC Torbjörn Gannholm <torbjorn.gannholm@gmail.com>
` Re: Incorrect result in certain expressions of anti-join
2025-01-07 22:03 UTC Pantelis Theodosiou <ypercube@gmail.com>
` Re: Incorrect result in certain expressions of anti-join
2025-01-07 23:19 UTC David G. Johnston <david.g.johnston@gmail.com>
[3+ messages in thread]
BUG #18767: Inconsistency in result of a Plpgsql GET DIAGNOSTICS PG_CONTEXT instruction.
2025-01-06 08:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18767: Inconsistency in result of a Plpgsql GET DIAGNOSTICS PG_CONTEXT instruction.
2025-01-06 16:24 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: BUG #18767: Inconsistency in result of a Plpgsql GET DIAGNOSTICS PG_CONTEXT instruction.
2025-01-07 10:32 UTC Philippe BEAUDOIN <phb.emaj@free.fr>
` Re: BUG #18767: Inconsistency in result of a Plpgsql GET DIAGNOSTICS PG_CONTEXT instruction.
2025-01-07 11:27 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: BUG #18767: Inconsistency in result of a Plpgsql GET DIAGNOSTICS PG_CONTEXT instruction.
2025-01-07 15:54 UTC Philippe BEAUDOIN <phb.emaj@free.fr>
[5+ messages in thread]
TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres'
2024-11-07 08:32 UTC Aleksander Alekseev <aleksander@timescale.com>
` Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres'
2024-11-07 13:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres'
2024-11-07 14:38 UTC Aleksander Alekseev <aleksander@timescale.com>
` Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres'
2024-11-07 15:09 UTC Aleksander Alekseev <aleksander@timescale.com>
` Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres'
2024-12-10 00:26 UTC Michael Paquier <michael@paquier.xyz>
` Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres'
2024-12-10 02:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres'
2024-12-11 02:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres'
2024-12-11 20:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres'
2024-12-11 22:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres'
2024-12-12 06:40 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres'
2024-12-12 23:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres'
2025-01-07 12:39 UTC Aleksander Alekseev <aleksander@timescale.com>
[12+ messages in thread]
BUG #18763: pg_get_viewdef returns an old def with new relation name
2025-01-02 06:43 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18763: pg_get_viewdef returns an old def with new relation name
2025-01-04 07:14 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #18763: pg_get_viewdef returns an old def with new relation name
2025-01-07 03:13 UTC lyz <linyuzhe.lyz@gmail.com>
[3+ messages in thread]
BUG #18766: not exists sometimes gives too few records
2025-01-03 17:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18766: not exists sometimes gives too few records
2025-01-03 19:01 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #18766: not exists sometimes gives too few records
2025-01-04 11:43 UTC Tomas Vondra <tomas@vondra.me>
` Re: BUG #18766: not exists sometimes gives too few records
2025-01-04 12:15 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18766: not exists sometimes gives too few records
2025-01-06 08:24 UTC Jan Kort <jan.kort@genetics.nl>
[5+ messages in thread]
回复：Re: Incorrect sort result caused by ROLLUP and WHERE operation
2025-01-03 01:12 UTC 谭忠涛 <zhongtao.tan@seaboxdata.com>
` 回复：Re: Incorrect sort result caused by ROLLUP and WHERE operation
2025-01-03 01:17 UTC 谭忠涛 <zhongtao.tan@seaboxdata.com>
[2+ messages in thread]
Incorrect sort result caused by ROLLUP and WHERE operation
2025-01-02 07:28 UTC 谭忠涛 <zhongtao.tan@seaboxdata.com>
` Re: Incorrect sort result caused by ROLLUP and WHERE operation
2025-01-02 10:49 UTC Zhang Mingli <zmlpostgres@gmail.com>
` Re: Incorrect sort result caused by ROLLUP and WHERE operation
2025-01-02 16:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
AW: Commit 5a2fed911a broke parallel query
2025-01-02 09:33 UTC Rank, Christian (LfL) <Christian.Rank@lfl.bayern.de>
` Re: AW: Commit 5a2fed911a broke parallel query
2025-01-02 15:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Column changes such as an increase in varchar size, can cause extremely slow queries, and postgres should run analyze automatically.
2024-10-31 18:34 UTC Tyler <tyhou13@gmx.com>
` Re: Column changes such as an increase in varchar size, can cause extremely slow queries, and postgres should run analyze automatically.
2024-11-01 06:32 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Column changes such as an increase in varchar size, can cause extremely slow queries, and postgres should run analyze automatically.
2024-11-01 09:03 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Column changes such as an increase in varchar size, can cause extremely slow queries, and postgres should run analyze automatically.
2025-01-02 05:29 UTC Noah Misch <noah@leadboat.com>
[4+ messages in thread]
BUG #18762: Update script produces distinct outputs before and after vacuum analyze operation
2025-01-01 19:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18762: Update script produces distinct outputs before and after vacuum analyze operation
2025-01-01 20:12 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18754: Logical replication cannot restart if client sent a copyDone
2024-12-27 12:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18754: Logical replication cannot restart if client sent a copyDone
2025-01-01 10:14 UTC vignesh C <vignesh21@gmail.com>
[2+ messages in thread]
BUG #18719: Bug Report for Patch (For inplace update durability, make heap_update() callers wait)
2024-11-21 10:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18719: Bug Report for Patch (For inplace update durability, make heap_update() callers wait)
2024-12-31 21:52 UTC Noah Misch <noah@leadboat.com>
[2+ messages in thread]
BUG #18761: Sequence Value Discrepancy After Running VACUUM ANALYZE
2024-12-31 09:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18761: Sequence Value Discrepancy After Running VACUUM ANALYZE
2024-12-31 13:42 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18761: Sequence Value Discrepancy After Running VACUUM ANALYZE
2024-12-31 15:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #18757: string_agg function(text, text) design issue
2024-12-30 06:22 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18757: string_agg function(text, text) design issue
2024-12-30 22:13 UTC David Rowley <dgrowleyml@gmail.com>
[2+ messages in thread]
BUG #18759: Missing files
2024-12-30 16:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18759: Missing files
2024-12-30 20:03 UTC Devrim Gündüz <devrim@gunduz.org>
[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