pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedOut of the box, full text search feature suggestion for postgresql
2023-12-28 15:15 UTC aa <ghevge@gmail.com>
` Re: Out of the box, full text search feature suggestion for postgresql
2023-12-28 16:46 UTC Bruce Momjian <bruce@momjian.us>
` Re: Out of the box, full text search feature suggestion for postgresql
2023-12-28 17:15 UTC aa <ghevge@gmail.com>
` Re: Out of the box, full text search feature suggestion for postgresql
2024-01-02 17:20 UTC Artur Zakirov <zaartur@gmail.com>
` Re: Out of the box, full text search feature suggestion for postgresql
2024-01-02 17:56 UTC aa <ghevge@gmail.com>
[5+ messages in thread]
BUG #18266: Restore process request way too many archive log files via pgbackrest
2024-01-02 13:38 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18265: jsonb comparison order is inconsistent
2024-01-02 09:09 UTC PG Bug reporting form <noreply@postgresql.org>
Segmentation fault caused by Postgrest - reateplan.c:6178 - prepare_sort_from_pathkeys
2023-12-31 11:32 UTC Michael B. Williams <Michael.Williams@glexia.com>
` Re: Segmentation fault caused by Postgrest - reateplan.c:6178 - prepare_sort_from_pathkeys
2024-01-01 13:04 UTC Michael B. Williams <Michael.Williams@glexia.com>
` Re: Segmentation fault caused by Postgrest - reateplan.c:6178 - prepare_sort_from_pathkeys
2024-01-01 15:14 UTC Magnus Hagander <magnus@hagander.net>
` Re: Segmentation fault caused by Postgrest - reateplan.c:6178 - prepare_sort_from_pathkeys
2024-01-02 03:18 UTC John Naylor <johncnaylorls@gmail.com>
[4+ messages in thread]
BUG #18262: Connecting ODI
2023-12-27 16:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18262: Connecting ODI
2023-12-27 21:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Fix error of negative bitmapset member
2023-12-27 14:06 UTC ywgrit <yw987194828@gmail.com>
BUG #18253: aarch64 oel 7 repomd.xml: [Errno 14] HTTPS Error 404
2023-12-20 08:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18253: aarch64 oel 7 repomd.xml: [Errno 14] HTTPS Error 404
2023-12-21 07:27 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18253: aarch64 oel 7 repomd.xml: [Errno 14] HTTPS Error 404
2023-12-26 09:12 UTC happygo@duck.com
[3+ messages in thread]
Issue with Running VACUUM on Database with Large Tables
2023-12-25 12:10 UTC Nagaraj Raj <nagaraj.sf@yahoo.com>
` Re: Issue with Running VACUUM on Database with Large Tables
2023-12-25 14:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-07 17:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-08 15:42 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-08 17:18 UTC Zu-Ming Jiang <zuming.jiang@inf.ethz.ch>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-09 03:54 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-09 04:51 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-09 11:08 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-09 11:21 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-09 12:25 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-10 08:20 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-10 21:02 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-20 08:49 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-22 02:32 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-22 08:59 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-27 17:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-28 07:03 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-28 08:03 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-28 08:24 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-11-30 07:21 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-12-05 02:35 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-12-07 02:55 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-12-12 06:41 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-12-22 23:27 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-12-24 23:37 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN
2023-12-25 07:18 UTC Richard Guo <guofenglinux@gmail.com>
[24+ messages in thread]
BUG #18258: The redo of the drop db wal needs to forward the Min Recovery Point
2023-12-24 15:02 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18257: Failed to build postgres, error occurred during linking
2023-12-23 05:37 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18257: Failed to build postgres, error occurred during linking
2023-12-23 08:22 UTC Haorong Xu <db_haorong@outlook.com>
[2+ messages in thread]
BUG #18256: spgGetCache() attempts to read to read invalid file for index attached to partitioned table
2023-12-21 14:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18256: spgGetCache() attempts to read to read invalid file for index attached to partitioned table
2023-12-21 16:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access
2023-12-09 16:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access
2023-12-10 09:55 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access
2023-12-10 12:19 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access
2023-12-11 12:53 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access
2023-12-12 09:50 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access
2023-12-12 13:16 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
` Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access
2023-12-13 01:40 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access
2023-12-13 03:36 UTC jian he <jian.universality@gmail.com>
` Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access
2023-12-21 13:26 UTC Dean Rasheed <dean.a.rasheed@gmail.com>
[9+ messages in thread]
BUG #18255: I am unable to deselect the stack bulider when i was install the postgresql
2023-12-21 11:11 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18254: could not load library llvmjit.so，Undefined symbol "_ZN4llvm12MemoryBuffer7getFileERKNS_5TwineEbbbSt
2023-12-20 10:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18254: could not load library llvmjit.so，Undefined symbol "_ZN4llvm12MemoryBuffer7getFileERKNS_5TwineEbbbSt
2023-12-20 21:02 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18254: could not load library llvmjit.so，Undefined symbol "_ZN4llvm12MemoryBuffer7getFileERKNS_5TwineEbbbSt
2023-12-21 02:31 UTC Xiaoming <yangxiaoming2019@gmail.com>
[3+ messages in thread]
BUG #18247: Integer overflow leads to negative width
2023-12-14 04:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-14 10:34 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-14 10:57 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-14 14:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-15 02:28 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-15 03:13 UTC RekGRpth <rekgrpth@gmail.com>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-15 03:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-15 06:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-15 12:01 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-15 15:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-15 15:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-16 15:24 UTC RekGRpth <rekgrpth@gmail.com>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-18 05:45 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-18 08:43 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-18 09:12 UTC Junwang Zhao <zhjwpku@gmail.com>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-18 21:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-19 03:32 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-19 04:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-19 05:53 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-19 15:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18247: Integer overflow leads to negative width
2023-12-20 02:05 UTC Richard Guo <guofenglinux@gmail.com>
[21+ messages in thread]
BUG #18246: pgstathashindex() attempts to read invalid file for hash index attached to partitioned table
2023-12-13 09:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18246: pgstathashindex() attempts to read invalid file for hash index attached to partitioned table
2023-12-13 14:18 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18246: pgstathashindex() attempts to read invalid file for hash index attached to partitioned table
2023-12-13 18:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18246: pgstathashindex() attempts to read invalid file for hash index attached to partitioned table
2023-12-15 13:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18246: pgstathashindex() attempts to read invalid file for hash index attached to partitioned table
2023-12-19 09:20 UTC Michael Paquier <michael@paquier.xyz>
[5+ messages in thread]
BUG #18249: pg_dump/pg_restore single schema with function1 calling function2
2023-12-15 09:09 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18249: pg_dump/pg_restore single schema with function1 calling function2
2023-12-15 13:03 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` BUG #18249: pg_dump/pg_restore single schema with function1 calling function2
2023-12-15 14:29 UTC Wetmore, Matthew (CTR) <Matthew.Wetmore@express-scripts.com>
` Re: BUG #18249: pg_dump/pg_restore single schema with function1 calling function2
2023-12-18 10:19 UTC <wilma.wantren@eclipso.de>
[4+ messages in thread]
BUG #18251: Incorrect DROP VIEW pg_catalog.* behavior
2023-12-17 09:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18251: Incorrect DROP VIEW pg_catalog.* behavior
2023-12-17 12:33 UTC Julien Rouhaud <rjuju123@gmail.com>
[2+ messages in thread]
答复: about psql copy ,we would like to seek help,Thanks.
2023-12-15 08:47 UTC 高升 <13325718563@189.cn>
BUG #18245: pg_restore accepts same output file name as input file name
2023-12-13 03:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18245: pg_restore accepts same output file name as input file name
2023-12-13 08:44 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18245: pg_restore accepts same output file name as input file name
2023-12-14 14:38 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #18245: pg_restore accepts same output file name as input file name
2023-12-14 14:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #18248: Expression is always zero
2023-12-14 05:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18248: Expression is always zero
2023-12-14 11:08 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18248: Expression is always zero
2023-12-14 11:10 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #18248: Expression is always zero
2023-12-14 11:11 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18248: Expression is always zero
2023-12-14 14:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #18244: Corruption in indexes involving whole-row expressions
2023-12-12 19:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18244: Corruption in indexes involving whole-row expressions
2023-12-12 22:53 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18244: Corruption in indexes involving whole-row expressions
2023-12-13 01:38 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18244: Corruption in indexes involving whole-row expressions
2023-12-13 03:55 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18244: Corruption in indexes involving whole-row expressions
2023-12-13 04:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18244: Corruption in indexes involving whole-row expressions
2023-12-14 05:43 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18244: Corruption in indexes involving whole-row expressions
2023-12-14 08:27 UTC Junwang Zhao <zhjwpku@gmail.com>
` Re: BUG #18244: Corruption in indexes involving whole-row expressions
2023-12-14 08:44 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[8+ messages in thread]
about psql copy ,we would like to seek help,Thanks.
2023-12-14 01:04 UTC 高升 <13325718563@189.cn>
` Re: about psql copy ,we would like to seek help,Thanks.
2023-12-14 01:26 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: about psql copy ,we would like to seek help,Thanks.
2023-12-14 08:08 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: about psql copy ,we would like to seek help,Thanks.
2023-12-14 08:14 UTC Christophe Pettus <xof@thebuild.com>
[4+ messages in thread]
BUG #18241: PushTransaction may cause Standby to execute ItemIdMarkDead
2023-12-11 12:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re:BUG #18241: PushTransaction may cause Standby to execute ItemIdMarkDead
2023-12-11 12:13 UTC feichanghong <feichanghong@qq.com>
` Re: BUG #18241: PushTransaction may cause Standby to execute ItemIdMarkDead
2023-12-12 04:49 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #18241: PushTransaction may cause Standby to execute ItemIdMarkDead
2023-12-12 08:57 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18241: PushTransaction may cause Standby to execute ItemIdMarkDead
2023-12-12 17:11 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18241: PushTransaction may cause Standby to execute ItemIdMarkDead
2023-12-13 00:46 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #18241: PushTransaction may cause Standby to execute ItemIdMarkDead
2023-12-13 14:13 UTC Michael Paquier <michael@paquier.xyz>
[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