pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedjsonb_jsonpath test fails after 2024-11-03
2024-10-30 14:55 UTC Bernhard M. Wiedemann <bwiedemann@suse.de>
` Re: jsonb_jsonpath test fails after 2024-11-03
2024-10-30 15:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18676: Execute function while selecting from table with partial index using this function.
2024-10-28 14:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18676: Execute function while selecting from table with partial index using this function.
2024-10-28 15:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18676: Execute function while selecting from table with partial index using this function.
2024-10-29 05:09 UTC Muhammad Waqas <waqas.m@bitnine.net>
[3+ messages in thread]
BUG #18674: Partitioned table doesn't depend on access method it uses
2024-10-26 06:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18674: Partitioned table doesn't depend on access method it uses
2024-10-27 07:53 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #18674: Partitioned table doesn't depend on access method it uses
2024-10-27 20:23 UTC Kirill Reshke <reshkekirill@gmail.com>
` Re: BUG #18674: Partitioned table doesn't depend on access method it uses
2024-10-28 07:23 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18674: Partitioned table doesn't depend on access method it uses
2024-10-28 08:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18674: Partitioned table doesn't depend on access method it uses
2024-10-28 11:49 UTC Junwang Zhao <zhjwpku@gmail.com>
` Re: BUG #18674: Partitioned table doesn't depend on access method it uses
2024-10-28 22:48 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18674: Partitioned table doesn't depend on access method it uses
2024-10-29 02:17 UTC Michael Paquier <michael@paquier.xyz>
[8+ messages in thread]
BUG #18672: failing to link postgresql
2024-10-24 18:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18672: failing to link postgresql
2024-10-24 20:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18672: failing to link postgresql
2024-10-28 10:49 UTC Thierry Bastian <bastian.thierry@laposte.net>
[3+ messages in thread]
BUG #18668: [Windows] September 2024 releases (17.0, 16.4, etc) all include older libiconv-2.dll
2024-10-21 15:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18668: [Windows] September 2024 releases (17.0, 16.4, etc) all include older libiconv-2.dll
2024-10-25 11:20 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` Re: BUG #18668: [Windows] September 2024 releases (17.0, 16.4, etc) all include older libiconv-2.dll
2024-10-28 10:00 UTC Kritika Agarwal <kritika.agarwal@enterprisedb.com>
[3+ messages in thread]
Installation Error: Column d.Dtaiculocale dose not exist Line 8
2024-10-26 16:34 UTC BRAD BLANSKI <odin_art@msn.com>
` Re: Installation Error: Column d.Dtaiculocale dose not exist Line 8
2024-10-28 04:56 UTC Muhammad Waqas <waqas.m@bitnine.net>
[2+ messages in thread]
BUG #18614: [ECPG] out of bound in DecodeDateTime
2024-09-12 08:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18614: [ECPG] out of bound in DecodeDateTime
2024-10-14 21:52 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18614: [ECPG] out of bound in DecodeDateTime
2024-10-16 00:18 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18614: [ECPG] out of bound in DecodeDateTime
2024-10-17 17:29 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18614: [ECPG] out of bound in DecodeDateTime
2024-10-18 05:51 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18614: [ECPG] out of bound in DecodeDateTime
2024-10-22 05:53 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18614: [ECPG] out of bound in DecodeDateTime
2024-10-22 23:37 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18614: [ECPG] out of bound in DecodeDateTime
2024-10-24 09:09 UTC Павел Некрасов <p.nekrasov@fobos-nt.ru>
` Re: BUG #18614: [ECPG] out of bound in DecodeDateTime
2024-10-24 22:25 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18614: [ECPG] out of bound in DecodeDateTime
2024-10-25 06:23 UTC Павел Некрасов <p.nekrasov@fobos-nt.ru>
` Re: BUG #18614: [ECPG] out of bound in DecodeDateTime
2024-10-25 09:39 UTC Matthias Apitz <guru@unixarea.de>
` Re: BUG #18614: [ECPG] out of bound in DecodeDateTime
2024-10-26 14:14 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[12+ messages in thread]
BUG #18673: Uninstallation of second instance
2024-10-25 13:38 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-01 13:50 UTC PG Bug reporting form <noreply@postgresql.org>
` RE: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-04 04:30 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-04 07:44 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-04 13:57 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-04 14:07 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-08 09:22 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-08 13:08 UTC Maxim Boguk <maxim.boguk@gmail.com>
` RE: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-09 05:31 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-09 10:44 UTC vignesh C <vignesh21@gmail.com>
` RE: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-09 12:34 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-14 06:25 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-14 12:33 UTC Maxim Boguk <maxim.boguk@gmail.com>
` RE: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-23 09:59 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` RE: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-23 10:12 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-24 08:46 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-25 00:41 UTC Peter Smith <smithpb2250@gmail.com>
` Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-25 03:26 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-25 04:38 UTC Peter Smith <smithpb2250@gmail.com>
` RE: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-25 06:51 UTC Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
` Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
2024-10-25 10:26 UTC Amit Kapila <amit.kapila16@gmail.com>
[20+ messages in thread]
BUG #18671: Unable to Run PostgreSQL on EndeavourOS without Modifying visudo
2024-10-24 14:30 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18671: Unable to Run PostgreSQL on EndeavourOS without Modifying visudo
2024-10-24 15:31 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18670: Can't install success, the cluster always failed
2024-10-24 08:11 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18669: pg_get_shmem_allocations show wrong memory for 11 structures
2024-10-23 15:15 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18658: Assert in SerialAdd() due to race condition
2024-10-16 15:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18658: Assert in SerialAdd() due to race condition
2024-10-17 05:47 UTC Andrew Bille <andrewbille@gmail.com>
` Re: BUG #18658: Assert in SerialAdd() due to race condition
2024-10-18 08:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18658: Assert in SerialAdd() due to race condition
2024-10-18 20:15 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18658: Assert in SerialAdd() due to race condition
2024-10-19 09:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18658: Assert in SerialAdd() due to race condition
2024-10-21 08:02 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #18658: Assert in SerialAdd() due to race condition
2024-10-23 13:31 UTC Maxim Orlov <orlovmg@gmail.com>
[7+ messages in thread]
BUG #18664: Assert in BeginCopyTo() fails when source DML query rewritten with notifying rule
2024-10-20 19:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18664: Assert in BeginCopyTo() fails when source DML query rewritten with notifying rule
2024-10-21 12:52 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18664: Assert in BeginCopyTo() fails when source DML query rewritten with notifying rule
2024-10-21 17:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18664: Assert in BeginCopyTo() fails when source DML query rewritten with notifying rule
2024-10-22 01:38 UTC Tender Wang <tndrwang@gmail.com>
[4+ messages in thread]
BUG #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]
[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