pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18666: Standby cluster does not start after building from Primary cluster.
2024-10-21 10:33 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18666: Standby cluster does not start after building from Primary cluster.
2024-10-21 14:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18666: Standby cluster does not start after building from Primary cluster.
2024-10-22 01:17 UTC px shi <spxlyy123@gmail.com>
` Re: BUG #18666: Standby cluster does not start after building from Primary cluster.
2024-10-22 01:32 UTC David G. Johnston <david.g.johnston@gmail.com>
[4+ messages in thread]
pg_ident.conf + regular expressions issue
2024-10-21 09:43 UTC Alexey Shishkin <alexey.shishkin.01@gmail.com>
` Re: pg_ident.conf + regular expressions issue
2024-10-21 14:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` pg_ident.conf + regular expressions issue
2024-10-21 15:09 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: pg_ident.conf + regular expressions issue
2024-10-21 15:37 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: pg_ident.conf + regular expressions issue
2024-10-21 15:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_ident.conf + regular expressions issue
2024-10-21 19:16 UTC Alexey Shishkin <alexey.shishkin.01@gmail.com>
` Re: pg_ident.conf + regular expressions issue
2024-10-21 19:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_ident.conf + regular expressions issue
2024-10-21 20:58 UTC Alexey Shishkin <alexey.shishkin.01@gmail.com>
` Re: pg_ident.conf + regular expressions issue
2024-10-21 21:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_ident.conf + regular expressions issue
2024-10-21 21:12 UTC David G. Johnston <david.g.johnston@gmail.com>
[10+ messages in thread]
Logical Replica ReorderBuffer Size Accounting Issues
2023-01-05 11:56 UTC Alex Richman <alexrichman@onesignal.com>
` Re: Logical Replica ReorderBuffer Size Accounting Issues
2023-01-06 04:03 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical Replica ReorderBuffer Size Accounting Issues
2023-01-06 16:35 UTC Alex Richman <alexrichman@onesignal.com>
` RE: Logical Replica ReorderBuffer Size Accounting Issues
2023-01-09 12:29 UTC wangw.fnst@fujitsu.com <wangw.fnst@fujitsu.com>
` Re: Logical Replica ReorderBuffer Size Accounting Issues
2023-01-09 16:00 UTC Alex Richman <alexrichman@onesignal.com>
` RE: Logical Replica ReorderBuffer Size Accounting Issues
2023-01-10 11:21 UTC wangw.fnst@fujitsu.com <wangw.fnst@fujitsu.com>
` Re: Logical Replica ReorderBuffer Size Accounting Issues
2023-01-11 15:41 UTC Alex Richman <alexrichman@onesignal.com>
` RE: Logical Replica ReorderBuffer Size Accounting Issues
2023-01-12 10:44 UTC wangw.fnst@fujitsu.com <wangw.fnst@fujitsu.com>
` Re: Logical Replica ReorderBuffer Size Accounting Issues
2023-01-12 13:01 UTC Alex Richman <alexrichman@onesignal.com>
` RE: Logical Replica ReorderBuffer Size Accounting Issues
2023-01-13 11:17 UTC wangw.fnst@fujitsu.com <wangw.fnst@fujitsu.com>
` Re: Logical Replica ReorderBuffer Size Accounting Issues
2023-01-13 12:15 UTC Alex Richman <alexrichman@onesignal.com>
` Re: Logical Replica ReorderBuffer Size Accounting Issues
2023-01-18 10:10 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical Replica ReorderBuffer Size Accounting Issues
2023-01-18 11:16 UTC Alex Richman <alexrichman@onesignal.com>
` Re: Logical Replica ReorderBuffer Size Accounting Issues
2023-02-16 19:08 UTC Alex Richman <alexrichman@onesignal.com>
` Re: Logical Replica ReorderBuffer Size Accounting Issues
2023-02-27 22:34 UTC Gilles Darold <gilles@darold.net>
` Re: Logical Replica ReorderBuffer Size Accounting Issues
2023-05-09 01:33 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: Logical Replica ReorderBuffer Size Accounting Issues
2023-05-09 09:06 UTC Wei Wang (Fujitsu) <wangw.fnst@fujitsu.com>
` Re: Logical Replica ReorderBuffer Size Accounting Issues
2023-05-09 14:57 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: Logical Replica ReorderBuffer Size Accounting Issues
2023-05-23 04:11 UTC Wei Wang (Fujitsu) <wangw.fnst@fujitsu.com>
` Re: Logical Replica ReorderBuffer Size Accounting Issues
2023-05-24 01:27 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` RE: Logical Replica ReorderBuffer Size Accounting Issues
2023-05-24 10:13 UTC Wei Wang (Fujitsu) <wangw.fnst@fujitsu.com>
` Re: Logical Replica ReorderBuffer Size Accounting Issues
2024-05-20 07:02 UTC torikoshia <torikoshia@oss.nttdata.com>
` Re: Logical Replica ReorderBuffer Size Accounting Issues
2024-10-16 20:51 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: Logical Replica ReorderBuffer Size Accounting Issues
2024-10-21 16:32 UTC Alex Richman <alexrichman@onesignal.com>
[24+ messages in thread]
BUG #18665: Breaking a foreign constraint: the error message may be more detailed
2024-10-21 01:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18665: Breaking a foreign constraint: the error message may be more detailed
2024-10-21 16:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18667: Default Permission Role Group
2024-10-21 10:56 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18667: Default Permission Role Group
2024-10-21 12:53 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-15 11:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-15 22:24 UTC Fabio R. Sluzala <fabio3rs@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-16 00:19 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-16 00:35 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-16 08:20 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-16 09:04 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-16 09:06 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-16 09:11 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-16 09:14 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-16 09:18 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-16 12:00 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-16 14:14 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-16 14:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-17 00:38 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-17 00:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-17 03:52 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-17 04:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-17 04:18 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-17 08:15 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-17 20:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-18 01:34 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-18 01:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-18 02:04 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-18 02:07 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-18 04:38 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-18 05:03 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-18 06:14 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-18 17:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-19 03:12 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-19 16:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18657: Using JSON_OBJECTAGG with volatile function leads to segfault
2024-10-20 03:41 UTC Amit Langote <amitlangote09@gmail.com>
[31+ messages in thread]
BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
2024-07-19 09:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
2024-07-19 19:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
2024-07-29 08:24 UTC Андрей Рачицкий <therealgofman@mail.ru>
` Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
2024-07-31 22:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
2024-08-01 00:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
2024-08-04 22:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
2024-08-05 00:46 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
2024-08-05 00:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
2024-08-06 18:48 UTC Robert Haas <robertmhaas@gmail.com>
` Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
2024-08-06 18:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
2024-09-17 23:47 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
2024-09-18 00:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
2024-09-19 03:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
2024-09-19 21:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
2024-10-19 23:28 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #18545: \dt breaks transaction, calling error when executed in SET SESSION AUTHORIZATION
2024-10-19 23:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
[16+ messages in thread]
BUG #18661: Libcurl.dll could not be found
2024-10-17 12:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18661: Libcurl.dll could not be found
2024-10-18 04:36 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
[2+ messages in thread]
Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-09-22 11:58 UTC Craig Milhiser <craig@milhiser.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-09-22 15:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-09-23 00:52 UTC Craig Milhiser <craig@milhiser.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-09-23 01:46 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-09-23 02:23 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-09-24 01:43 UTC Craig Milhiser <craig@milhiser.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-09-29 23:03 UTC Craig Milhiser <craig@milhiser.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-09-30 01:14 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-02 00:12 UTC Craig Milhiser <craig@milhiser.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-02 00:44 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-07 11:42 UTC Craig Milhiser <craig@milhiser.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-08 09:16 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-09 16:28 UTC Craig Milhiser <craig@milhiser.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-09 19:54 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-10 03:59 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-13 11:23 UTC Craig Milhiser <craig@milhiser.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-13 21:08 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-14 05:45 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-14 06:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-14 09:16 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-15 16:43 UTC Craig Milhiser <craig@milhiser.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-16 09:19 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-17 08:12 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-17 08:57 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-17 09:48 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-17 23:34 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
2024-10-17 23:59 UTC Andrei Lepikhov <lepihov@gmail.com>
[27+ messages in thread]
BUG #18662: ORDER BY after GROUPING SETS does not order correctly for certain WHERE condition
2024-10-17 12:56 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18662: ORDER BY after GROUPING SETS does not order correctly for certain WHERE condition
2024-10-17 15:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18660: information_schema.columns.ordinal_position has gaps when primary key columns are dropped
2024-10-17 08:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18660: information_schema.columns.ordinal_position has gaps when primary key columns are dropped
2024-10-17 14:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18660: information_schema.columns.ordinal_position has gaps when primary key columns are dropped
2024-10-17 15:02 UTC Erik Wienhold <ewie@ewie.name>
[3+ messages in thread]
BUG #18631: Brocken postgresql12-devel RPM
2024-09-25 05:48 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18631: Brocken postgresql12-devel RPM
2024-09-26 12:44 UTC Devrim Gündüz <devrim@gunduz.org>
` Re: BUG #18631: Brocken postgresql12-devel RPM
2024-10-06 22:52 UTC Devrim Gündüz <devrim@gunduz.org>
` Re: Re: BUG #18631: Brocken postgresql12-devel RPM
2024-10-17 07:45 UTC Lukas_Lerner@gmx.at
[4+ messages in thread]
BUG #18659: Need support on disable database queries to memory dump
2024-10-17 07:17 UTC PG Bug reporting form <noreply@postgresql.org>
Performance Issue on Query 18 of TPC-H Benchmark
2024-10-15 18:28 UTC Ba Jinsheng <bajinsheng@u.nus.edu>
` Re: Performance Issue on Query 18 of TPC-H Benchmark
2024-10-15 21:56 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Performance Issue on Query 18 of TPC-H Benchmark
2024-10-15 23:21 UTC Alena Rybakina <a.rybakina@postgrespro.ru>
` Re: Performance Issue on Query 18 of TPC-H Benchmark
2024-10-16 05:58 UTC Ba Jinsheng <bajinsheng@u.nus.edu>
` Re: Performance Issue on Query 18 of TPC-H Benchmark
2024-10-16 06:28 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Performance Issue on Query 18 of TPC-H Benchmark
2024-10-16 14:01 UTC Alena Rybakina <a.rybakina@postgrespro.ru>
` Re: Performance Issue on Query 18 of TPC-H Benchmark
2024-10-16 14:56 UTC Ba Jinsheng <bajinsheng@u.nus.edu>
` Re: Performance Issue on Query 18 of TPC-H Benchmark
2024-10-16 16:42 UTC Alena Rybakina <a.rybakina@postgrespro.ru>
` Re: Performance Issue on Query 18 of TPC-H Benchmark
2024-10-16 18:26 UTC Ba Jinsheng <bajinsheng@u.nus.edu>
` Re: Performance Issue on Query 18 of TPC-H Benchmark
2024-10-17 02:14 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Performance Issue on Query 18 of TPC-H Benchmark
2024-10-17 02:51 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Performance Issue on Query 18 of TPC-H Benchmark
2024-10-17 07:00 UTC Ba Jinsheng <bajinsheng@u.nus.edu>
[12+ messages in thread]
BUG #18656: "STABLE" function sometimes does not see changes
2024-10-15 09:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18656: "STABLE" function sometimes does not see changes
2024-10-15 17:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18656: "STABLE" function sometimes does not see changes
2024-10-16 21:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #18654: From fuzzystrmatch, levenshtein function with costs parameters produce incorrect results
2024-10-14 09:14 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18654: From fuzzystrmatch, levenshtein function with costs parameters produce incorrect results
2024-10-14 16:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18654: From fuzzystrmatch, levenshtein function with costs parameters produce incorrect results
2024-10-16 10:10 UTC bjdev.gthb@laposte.net
[3+ messages in thread]
BUG #18647: INSERT statements execute functions twice.
2024-10-08 19:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18647: INSERT statements execute functions twice.
2024-10-08 20:04 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18647: INSERT statements execute functions twice.
2024-10-08 20:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18647: INSERT statements execute functions twice.
2024-10-09 12:26 UTC Todd Brandys <brandystodd@gmail.com>
` Re: BUG #18647: INSERT statements execute functions twice.
2024-10-09 12:40 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18647: INSERT statements execute functions twice.
2024-10-09 13:55 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: BUG #18647: INSERT statements execute functions twice.
2024-10-09 14:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18647: INSERT statements execute functions twice.
2024-10-15 09:30 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[8+ messages in thread]
Question of Parallel Hash Join on TPC-H Benchmark
2024-10-10 14:11 UTC Ba Jinsheng <bajinsheng@u.nus.edu>
` Re: Question of Parallel Hash Join on TPC-H Benchmark
2024-10-10 14:16 UTC Ba Jinsheng <bajinsheng@u.nus.edu>
` Re: Question of Parallel Hash Join on TPC-H Benchmark
2024-10-10 14:40 UTC Tomas Vondra <tomas@vondra.me>
` Re: Question of Parallel Hash Join on TPC-H Benchmark
2024-10-10 14:47 UTC Zhang Mingli <zmlpostgres@gmail.com>
` Re: Question of Parallel Hash Join on TPC-H Benchmark
2024-10-10 16:52 UTC Ba Jinsheng <bajinsheng@u.nus.edu>
` Re: Question of Parallel Hash Join on TPC-H Benchmark
2024-10-12 01:53 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Question of Parallel Hash Join on TPC-H Benchmark
2024-10-12 18:11 UTC Ba Jinsheng <bajinsheng@u.nus.edu>
` Re: Question of Parallel Hash Join on TPC-H Benchmark
2024-10-13 00:01 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Question of Parallel Hash Join on TPC-H Benchmark
2024-10-13 03:09 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Question of Parallel Hash Join on TPC-H Benchmark
2024-10-13 08:57 UTC Ba Jinsheng <bajinsheng@u.nus.edu>
` Re: Question of Parallel Hash Join on TPC-H Benchmark
2024-10-13 09:57 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: Question of Parallel Hash Join on TPC-H Benchmark
2024-10-14 06:52 UTC Ba Jinsheng <bajinsheng@u.nus.edu>
[12+ messages in thread]
BUG #18653: Is it necessary for ATExecDropInherit to acquire an AccessExclusiveLock on the parent table?
2024-10-13 07:23 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-09 21:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-09 21:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-10 03:52 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-10 04:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-10 06:50 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-10 09:02 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-10 10:20 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-10 10:23 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-10 10:41 UTC Alena Rybakina <a.rybakina@postgrespro.ru>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-10 11:57 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-11 02:43 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-11 04:25 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-11 08:02 UTC Alena Rybakina <a.rybakina@postgrespro.ru>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-11 10:42 UTC Alena Rybakina <a.rybakina@postgrespro.ru>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-11 20:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-12 04:13 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-12 06:05 UTC Andrei Lepikhov <lepihov@gmail.com>
` Re: BUG #18652: Planner can not find pathkey item to sort for query with expression and expression index
2024-10-12 19:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
[18+ messages in thread]
BUG #18646: The problem with the installer
2024-10-04 13:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18646: The problem with the installer
2024-10-04 14:00 UTC Даниил <28muskin06@gmail.com>
` Re: BUG #18646: The problem with the installer
2024-10-07 04:38 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` Re: BUG #18646: The problem with the installer
2024-10-07 15:32 UTC Zaid Shabbir <zaidshabbir@gmail.com>
` Re: BUG #18646: The problem with the installer
2024-10-12 15:06 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
[5+ messages in thread]
BUG #18648: When I restore the database on rockylinux9, I will use amcheck to check that there will be an abnorm
2024-10-09 00:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18648: When I restore the database on rockylinux9, I will use amcheck to check that there will be an abnorm
2024-10-09 08:40 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18648: When I restore the database on rockylinux9, I will use amcheck to check that there will be an abnorm
2024-10-10 01:02 UTC weijie JL <weijie1006jl@gmail.com>
[3+ messages in thread]
BUG #18650: rhel-8-aarch64 yum repository for Postgres 13 is missing repodata
2024-10-09 12:36 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18649: PG17 release note bug for "AS LOCAL"
2024-10-09 01:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18649: PG17 release note bug for "AS LOCAL"
2024-10-09 08:11 UTC Daniel Gustafsson <daniel@yesql.se>
[2+ messages in thread]
pg_dump throwing segfault error during backup
2024-10-08 05:40 UTC Cassandra Thrift <cssndrthrift@gmail.com>
` Re: pg_dump throwing segfault error during backup
2024-10-08 14:05 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