pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feed2000 times performance drop after pg14 upgrade when JIT = 1
2022-03-09 12:20 UTC Sergey Mirvoda <sergey@mirvoda.com>
Bug plperl.c
2022-02-22 17:49 UTC Mark Murawski <markm-lists@intellasoft.net>
` Re: Bug plperl.c
2022-02-22 19:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Bug plperl.c
2022-02-22 20:06 UTC Mark Murawski <markm-lists@intellasoft.net>
` Re: Bug plperl.c
2022-02-22 20:27 UTC Mark Murawski <markm-lists@intellasoft.net>
` Re: Bug plperl.c
2022-02-25 20:15 UTC Mark Murawski <markm-lists@intellasoft.net>
` Re: Bug plperl.c
2022-02-25 21:36 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Bug plperl.c
2022-03-08 19:59 UTC Mark Murawski <markm-lists@intellasoft.net>
` Re: Bug plperl.c
2022-03-08 21:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
[8+ messages in thread]
BUG #17428: last_value incorrect for uninitialized sequence
2022-03-07 00:31 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17428: last_value incorrect for uninitialized sequence
2022-03-07 13:35 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17428: last_value incorrect for uninitialized sequence
2022-03-07 14:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17428: last_value incorrect for uninitialized sequence
2022-03-07 15:14 UTC Glen Edmonds <glen.edmonds@gmail.com>
` Re: BUG #17428: last_value incorrect for uninitialized sequence
2022-03-07 15:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17428: last_value incorrect for uninitialized sequence
2022-03-07 15:40 UTC David G. Johnston <david.g.johnston@gmail.com>
[6+ messages in thread]
BUG #17427: ERROR: cannot cast type bytea to bigint
2022-03-06 06:29 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17427: ERROR: cannot cast type bytea to bigint
2022-03-06 23:35 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #17425: Postgres service does not start if path to data folder ends with backslash.
2022-03-04 10:14 UTC PG Bug reporting form <noreply@postgresql.org>
Cannot refresh materialized view concurrently if you have a column name called "mv"
2022-03-03 14:53 UTC Rupert Agnew <RAgnew@albacorecapital.com>
` Re: Cannot refresh materialized view concurrently if you have a column name called "mv"
2022-03-03 17:51 UTC Bruce Momjian <bruce@momjian.us>
[2+ messages in thread]
BUG #17424: Build failed on disabled GNUC in Clang environment CFLAGS= -O2 -fgnuc-version=0
2022-03-02 10:50 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17424: Build failed on disabled GNUC in Clang environment CFLAGS= -O2 -fgnuc-version=0
2022-03-02 14:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17422: Memory leak
2022-03-01 17:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17422: Memory leak
2022-03-01 20:21 UTC Andres Freund <andres@anarazel.de>
[2+ messages in thread]
Wal sender process not moving past wait_event_type: IO and wait_event: WALRead
2022-02-24 14:21 UTC Anurag Shrivastava <anurag.shrivastava@hevodata.com>
` Re: Wal sender process not moving past wait_event_type: IO and wait_event: WALRead
2022-02-25 01:51 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Wal sender process not moving past wait_event_type: IO and wait_event: WALRead
2022-02-25 01:59 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
[3+ messages in thread]
BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
2022-02-15 17:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
2022-02-15 20:51 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
2022-02-16 08:14 UTC Victor Yegorov <vyegorov@gmail.com>
` Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
2022-02-16 12:23 UTC John Naylor <john.naylor@enterprisedb.com>
` Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
2022-02-17 00:16 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
2022-02-17 02:52 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
2022-02-17 12:26 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
2022-02-17 16:29 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
2022-02-17 16:35 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
2022-02-21 17:57 UTC Victor Yegorov <vyegorov@gmail.com>
` Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
2022-02-23 15:36 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
2022-02-23 15:41 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
2022-02-24 15:18 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
2022-02-24 18:36 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade
2022-02-24 21:17 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
[15+ messages in thread]
BUG #17416: Server crashes due to python3 stack overflow on executing multiple plpy.rollback() calls
2022-02-23 11:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17416: Server crashes due to python3 stack overflow on executing multiple plpy.rollback() calls
2022-02-23 16:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17415: Unable to use underscore as first character in set_config custom parameter
2022-02-23 08:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17415: Unable to use underscore as first character in set_config custom parameter
2022-02-23 13:54 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #17415: Unable to use underscore as first character in set_config custom parameter
2022-02-23 15:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #17413: update of partitioned table via postgres_fdw updates to much rows
2022-02-22 10:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17413: update of partitioned table via postgres_fdw updates to much rows
2022-02-22 17:09 UTC Japin Li <japinli@hotmail.com>
` RE: BUG #17413: update of partitioned table via postgres_fdw updates to much rows
2022-02-22 17:28 UTC Stepan Yankevych <Stepan_Yankevych@epam.com>
` Re: BUG #17413: update of partitioned table via postgres_fdw updates to much rows
2022-02-23 07:40 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
[4+ messages in thread]
BUG #17414: install failed
2022-02-23 04:36 UTC PG Bug reporting form <noreply@postgresql.org>
Bug in execution of EXISTS and IN clauses for large tables
2022-02-22 13:17 UTC Martin Kos <martin.kos@molecularhealth.com>
` Re: Bug in execution of EXISTS and IN clauses for large tables
2022-02-22 14:17 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Bug in execution of EXISTS and IN clauses for large tables
2022-02-22 14:21 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Bug in execution of EXISTS and IN clauses for large tables
2022-02-22 15:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: Bug in execution of EXISTS and IN clauses for large tables
2022-02-22 16:16 UTC Martin Kos <martin.kos@molecularhealth.com>
` Re: Bug in execution of EXISTS and IN clauses for large tables
2022-02-22 23:33 UTC David Rowley <dgrowleyml@gmail.com>
[6+ messages in thread]
BUG #17412: CREATE INDEX on a partitioned table doesn't recognize existing partial indexes on partitions
2022-02-21 08:26 UTC PG Bug reporting form <noreply@postgresql.org>
Re all: Report some potential memory leak bugs in pg_dump.c
2022-02-19 08:04 UTC wliang@stu.xidian.edu.cn
` Re: Re all: Report some potential memory leak bugs in pg_dump.c
2022-02-19 11:10 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: Re: Re all: Report some potential memory leak bugs in pg_dump.c
2022-02-19 12:29 UTC wliang@stu.xidian.edu.cn
` Re: Re all: Report some potential memory leak bugs in pg_dump.c
2022-02-19 16:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
Report some potential memory leak bugs in pg_dump.c
2022-02-19 05:45 UTC wliang@stu.xidian.edu.cn
` Re: Report some potential memory leak bugs in pg_dump.c
2022-02-19 06:15 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Report some potential memory leak bugs in pg_dump.c
2022-02-19 07:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
pg_visibility's pg_check_visible() yields false positive when working in parallel with autovacuum
2022-02-17 21:09 UTC Daniel Shelepanov <deniel1495@mail.ru>
` Re: pg_visibility's pg_check_visible() yields false positive when working in parallel with autovacuum
2022-02-18 16:56 UTC Andres Freund <andres@anarazel.de>
` Re: pg_visibility's pg_check_visible() yields false positive when working in parallel with autovacuum
2022-02-18 17:51 UTC Andres Freund <andres@anarazel.de>
[3+ messages in thread]
BUG #17410: After upgrade to postgresql 12.9 from 12.6 , some of the statements having ”=” operator not returnin
2022-02-18 15:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17410: After upgrade to postgresql 12.9 from 12.6 , some of the statements having ”=” operator not returnin
2022-02-18 16:04 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17410: After upgrade to postgresql 12.9 from 12.6 , some of the statements having ”=” operator not returnin
2022-02-18 16:19 UTC Satish Nayak [NMC - IT] <satish.nayak@nmc.ae>
[3+ messages in thread]
Optimizer picking a poor plan for Serializable Transaction Isolation
2022-02-17 18:55 UTC Tyler Rockwood <tyler@shortwave.com>
` Re: Optimizer picking a poor plan for Serializable Transaction Isolation
2022-02-17 22:09 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
[2+ messages in thread]
Report a potential memory leak in setup_config()
2022-02-15 01:49 UTC wliang@stu.xidian.edu.cn
` Re: Report a potential memory leak in setup_config()
2022-02-15 12:10 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Report a potential memory leak in setup_config()
2022-02-15 16:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Report a potential memory leak in setup_config()
2022-02-16 01:29 UTC Andres Freund <andres@anarazel.de>
` Re: Report a potential memory leak in setup_config()
2022-02-16 01:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Report a potential memory leak in setup_config()
2022-02-16 02:21 UTC Andres Freund <andres@anarazel.de>
` Re: Report a potential memory leak in setup_config()
2022-02-16 02:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Report a potential memory leak in setup_config()
2022-02-16 02:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Report a potential memory leak in setup_config()
2022-02-16 04:10 UTC Andres Freund <andres@anarazel.de>
` Re: Report a potential memory leak in setup_config()
2022-02-16 04:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Report a potential memory leak in setup_config()
2022-02-16 07:13 UTC wliang@stu.xidian.edu.cn
` Re: Report a potential memory leak in setup_config()
2022-02-16 08:13 UTC wliang@stu.xidian.edu.cn
` Re: Report a potential memory leak in setup_config()
2022-02-16 15:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Report a potential memory leak in setup_config()
2022-02-16 17:37 UTC Andres Freund <andres@anarazel.de>
` Re: Report a potential memory leak in setup_config()
2022-02-16 17:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
[15+ messages in thread]
BUG #17407: trim trims more than expected
2022-02-16 10:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re:BUG #17407: trim trims more than expected
2022-02-16 11:03 UTC Sergei Kornilov <sk@zsrv.org>
` Re: BUG #17407: trim trims more than expected
2022-02-16 15:12 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[3+ messages in thread]
BUG #17408: Duplicate aliases silently fail
2022-02-16 10:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17408: Duplicate aliases silently fail
2022-02-16 12:02 UTC Pantelis Theodosiou <ypercube@gmail.com>
` Re: BUG #17408: Duplicate aliases silently fail
2022-02-16 12:05 UTC Kevin Potgieter <porturpotgieter@gmail.com>
` Re: BUG #17408: Duplicate aliases silently fail
2022-02-16 12:08 UTC John Naylor <john.naylor@enterprisedb.com>
` Re: BUG #17408: Duplicate aliases silently fail
2022-02-16 13:23 UTC David G. Johnston <david.g.johnston@gmail.com>
[5+ messages in thread]
Postgres 13.5 out parameter argument with explicit cast fails with argument is not writable
2022-02-14 22:50 UTC Delaney, Ed <Ed.Delaney@ellucian.com>
` Re: Postgres 13.5 out parameter argument with explicit cast fails with argument is not writable
2022-02-14 23:24 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Postgres 13.5 out parameter argument with explicit cast fails with argument is not writable
2022-02-14 23:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgres 13.5 out parameter argument with explicit cast fails with argument is not writable
2022-02-15 18:12 UTC Delaney, Ed <Ed.Delaney@ellucian.com>
` Re: Postgres 13.5 out parameter argument with explicit cast fails with argument is not writable
2022-02-15 18:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ 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