pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17999: comment to BUG 17990 (PSQL Process hangs in parallel mode)
2023-06-26 07:06 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17995: Segmentation fault caused by UPDATE statement
2023-06-24 18:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17995: Segmentation fault caused by UPDATE statement
2023-06-24 19:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17995: Segmentation fault caused by UPDATE statement
2023-06-24 20:48 UTC Willian Colognesi <willian_colognesi@trimble.com>
` Re: BUG #17995: Segmentation fault caused by UPDATE statement
2023-06-25 03:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17995: Segmentation fault caused by UPDATE statement
2023-06-26 04:21 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17995: Segmentation fault caused by UPDATE statement
2023-06-26 04:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17995: Segmentation fault caused by UPDATE statement
2023-06-26 04:56 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17995: Segmentation fault caused by UPDATE statement
2023-06-26 05:00 UTC Alexander Lakhin <exclusion@gmail.com>
[8+ messages in thread]
BUG #17993: FK issue on logical replication table
2023-06-24 06:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17993: FK issue on logical replication table
2023-06-26 04:42 UTC Amit Kapila <amit.kapila16@gmail.com>
[2+ messages in thread]
回复: BUG #17998: Postgres crashes when executing WorkTableScan.
2023-06-26 03:53 UTC 梁 成林 <chenglin-liang@outlook.com>
BUG #17990: PSQL Process hangs in parallel mode
2023-06-22 20:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17990: PSQL Process hangs in parallel mode
2023-06-25 22:12 UTC Thomas Munro <thomas.munro@gmail.com>
[2+ messages in thread]
range canonicalization function make corner case failed.
2023-06-25 03:12 UTC jian he <jian.universality@gmail.com>
BUG #17991: FATAL: cannot request additional shared memory outside shmem_request_hook
2023-06-22 23:17 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17991: FATAL: cannot request additional shared memory outside shmem_request_hook
2023-06-23 09:37 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #17991: FATAL: cannot request additional shared memory outside shmem_request_hook
2023-06-23 11:09 UTC Julien Rouhaud <rjuju123@gmail.com>
[3+ messages in thread]
BUG #17992: Followed instructions to setup Postgresql but systemctl restart postgresql-15.service
2023-06-23 08:27 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17989: ERROR: could not open file "pg_logical/snapshots/6-1E182808.snap": Permission denied
2023-06-22 10:26 UTC PG Bug reporting form <noreply@postgresql.org>
Small subset of man pages available after install from Redhat-compatible repo
2023-06-21 21:16 UTC Linus Hicks <linus.hicks@highstreetit.com>
` Re: Small subset of man pages available after install from Redhat-compatible repo
2023-06-22 06:39 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
BUG #17988: psql generates segfault when connecting to remote database
2023-06-21 17:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17988: psql generates segfault when connecting to remote database
2023-06-21 20:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17987: zypper refresh failed when installed the postgresql
2023-06-21 09:17 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17987: zypper refresh failed when installed the postgresql
2023-06-21 11:17 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re:Re: BUG #17987: zypper refresh failed when installed the postgresql
2023-06-21 14:14 UTC 270246512 <270246512@qq.com>
` Re: Re: BUG #17987: zypper refresh failed when installed the postgresql
2023-06-21 16:08 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[4+ messages in thread]
BUG #17986: Inconsistent results of SELECT affected by btree index
2023-06-20 20:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17986: Inconsistent results of SELECT affected by btree index
2023-06-20 23:40 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #17986: Inconsistent results of SELECT affected by btree index
2023-06-21 04:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17986: Inconsistent results of SELECT affected by btree index
2023-06-21 07:22 UTC Zu-Ming Jiang <zuming.jiang@inf.ethz.ch>
` Re: BUG #17986: Inconsistent results of SELECT affected by btree index
2023-06-21 13:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #17978: Unexpected error: "wrong varnullingrels (b) (expected (b 5)) for Var 6/2" triggered by JOIN
2023-06-15 08:20 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17978: Unexpected error: "wrong varnullingrels (b) (expected (b 5)) for Var 6/2" triggered by JOIN
2023-06-17 19:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17978: Unexpected error: "wrong varnullingrels (b) (expected (b 5)) for Var 6/2" triggered by JOIN
2023-06-18 16:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17978: Unexpected error: "wrong varnullingrels (b) (expected (b 5)) for Var 6/2" triggered by JOIN
2023-06-19 10:21 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17978: Unexpected error: "wrong varnullingrels (b) (expected (b 5)) for Var 6/2" triggered by JOIN
2023-06-19 16:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17978: Unexpected error: "wrong varnullingrels (b) (expected (b 5)) for Var 6/2" triggered by JOIN
2023-06-19 20:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17978: Unexpected error: "wrong varnullingrels (b) (expected (b 5)) for Var 6/2" triggered by JOIN
2023-06-21 07:20 UTC Richard Guo <guofenglinux@gmail.com>
[7+ messages in thread]
BUG #17983: Assert IsTransactionState() failed when empty string statement prepared in aborted transaction
2023-06-19 19:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17983: Assert IsTransactionState() failed when empty string statement prepared in aborted transaction
2023-06-20 08:17 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #17983: Assert IsTransactionState() failed when empty string statement prepared in aborted transaction
2023-06-20 16:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17983: Assert IsTransactionState() failed when empty string statement prepared in aborted transaction
2023-06-21 01:45 UTC Japin Li <japinli@hotmail.com>
[4+ messages in thread]
BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-14 15:17 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-14 20:36 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-14 21:10 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-14 21:12 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-14 21:21 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-14 21:38 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-14 22:49 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-14 23:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-14 23:57 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-14 23:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-15 00:09 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-15 00:16 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-15 00:23 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-15 00:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-15 00:38 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-15 00:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-15 04:33 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17975: Nested Loop Index Scan returning wrong result
2023-06-20 23:01 UTC David Rowley <dgrowleyml@gmail.com>
[18+ messages in thread]
BUG #17985: Inconsistent results of SELECT comparing two CASE WHEN clause
2023-06-20 16:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17985: Inconsistent results of SELECT comparing two CASE WHEN clause
2023-06-20 18:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17985: Inconsistent results of SELECT comparing two CASE WHEN clause
2023-06-20 20:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #17984: Service stopped and cannot restart
2023-06-20 14:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17984: Service stopped and cannot restart
2023-06-20 16:34 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #17976: Inconsistent results of SELECT using CASE WHEN clause
2023-06-14 15:59 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17976: Inconsistent results of SELECT using CASE WHEN clause
2023-06-14 23:22 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17976: Inconsistent results of SELECT using CASE WHEN clause
2023-06-14 23:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17976: Inconsistent results of SELECT using CASE WHEN clause
2023-06-14 23:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17976: Inconsistent results of SELECT using CASE WHEN clause
2023-06-15 07:12 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17976: Inconsistent results of SELECT using CASE WHEN clause
2023-06-15 19:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17976: Inconsistent results of SELECT using CASE WHEN clause
2023-06-19 12:43 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #17976: Inconsistent results of SELECT using CASE WHEN clause
2023-06-19 13:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17976: Inconsistent results of SELECT using CASE WHEN clause
2023-06-20 09:25 UTC Amit Kapila <amit.kapila16@gmail.com>
[9+ messages in thread]
BUG #17974: Walsenders memory usage suddenly spike to 80G+ causing OOM and server reboot
2023-06-14 00:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17974: Walsenders memory usage suddenly spike to 80G+ causing OOM and server reboot
2023-06-14 01:23 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17974: Walsenders memory usage suddenly spike to 80G+ causing OOM and server reboot
2023-06-14 22:15 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17974: Walsenders memory usage suddenly spike to 80G+ causing OOM and server reboot
2023-06-15 00:04 UTC Michael Guissine <mguissine@gmail.com>
` Re: BUG #17974: Walsenders memory usage suddenly spike to 80G+ causing OOM and server reboot
2023-06-15 01:02 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17974: Walsenders memory usage suddenly spike to 80G+ causing OOM and server reboot
2023-06-15 01:06 UTC Michael Guissine <mguissine@gmail.com>
` Re: BUG #17974: Walsenders memory usage suddenly spike to 80G+ causing OOM and server reboot
2023-06-15 01:20 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17974: Walsenders memory usage suddenly spike to 80G+ causing OOM and server reboot
2023-06-19 19:36 UTC Michael Guissine <mguissine@gmail.com>
[8+ messages in thread]
BUG #17982: Inconsistent results of SELECT with CTE caused by subquery comparison
2023-06-19 12:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17982: Inconsistent results of SELECT with CTE caused by subquery comparison
2023-06-19 16:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17982: Inconsistent results of SELECT with CTE caused by subquery comparison
2023-06-19 18:00 UTC Zu-Ming Jiang <zuming.jiang@inf.ethz.ch>
[3+ messages in thread]
BUG #17981: HY000 server closed the connection unexpectedly
2023-06-19 11:52 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17981: HY000 server closed the connection unexpectedly
2023-06-19 13:34 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[2+ messages in thread]
Internal error with types changes and prepared statements
2021-09-22 18:13 UTC Daniele Varrazzo <daniele.varrazzo@gmail.com>
` Re: Internal error with types changes and prepared statements
2021-09-22 18:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Internal error with types changes and prepared statements
2021-09-22 18:32 UTC Daniele Varrazzo <daniele.varrazzo@gmail.com>
` Re: Internal error with types changes and prepared statements
2023-06-16 13:00 UTC Jelte Fennema <me@jeltef.nl>
[4+ messages in thread]
BUG #17964: Missed query planner optimization
2023-06-06 11:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17964: Missed query planner optimization
2023-06-06 21:32 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17964: Missed query planner optimization
2023-06-07 11:47 UTC Mathias Kunter <mathiaskunter@gmail.com>
` Re: BUG #17964: Missed query planner optimization
2023-06-07 12:36 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17964: Missed query planner optimization
2023-06-07 16:53 UTC Mathias Kunter <mathiaskunter@gmail.com>
` Re: BUG #17964: Missed query planner optimization
2023-06-15 15:53 UTC Mathias Kunter <mathiaskunter@gmail.com>
` Re: BUG #17964: Missed query planner optimization
2023-06-16 00:30 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17964: Missed query planner optimization
2023-06-16 12:56 UTC Mathias Kunter <mathiaskunter@gmail.com>
[8+ messages in thread]
BUG #17979: (pg_tsparser + ts_headline) duplicate output if dot present
2023-06-15 16:40 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17979: (pg_tsparser + ts_headline) duplicate output if dot present
2023-06-15 20:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
[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