pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedMemory leak on subquery as scalar operand
2022-10-30 17:13 UTC Lauri Laanmets <pcspets@gmail.com>
` Re: Memory leak on subquery as scalar operand
2022-10-31 13:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Memory leak on subquery as scalar operand
2022-10-31 14:16 UTC Lauri Laanmets <pcspets@gmail.com>
` Re: Memory leak on subquery as scalar operand
2022-10-31 23:20 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Memory leak on subquery as scalar operand
2022-11-01 00:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Memory leak on subquery as scalar operand
2022-11-01 03:48 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Memory leak on subquery as scalar operand
2022-11-01 04:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Memory leak on subquery as scalar operand
2022-11-01 04:26 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Memory leak on subquery as scalar operand
2022-11-01 04:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Memory leak on subquery as scalar operand
2022-11-01 05:51 UTC Andres Freund <andres@anarazel.de>
` Re: Memory leak on subquery as scalar operand
2022-11-02 08:26 UTC Lauri Laanmets <pcspets@gmail.com>
` Re: Memory leak on subquery as scalar operand
2023-02-22 19:43 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Memory leak on subquery as scalar operand
2023-05-02 13:33 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Memory leak on subquery as scalar operand
2023-05-16 13:31 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Memory leak on subquery as scalar operand
2023-09-13 13:24 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Memory leak on subquery as scalar operand
2023-09-27 12:07 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Memory leak on subquery as scalar operand
2023-09-27 20:45 UTC Andres Freund <andres@anarazel.de>
` Re: Memory leak on subquery as scalar operand
2023-11-17 15:31 UTC Daniel Gustafsson <daniel@yesql.se>
[18+ messages in thread]
BUG #18202: pg_constraint data isn't refreshed when using alter rename to on a constraint trigger
2023-11-17 14:31 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18202: pg_constraint data isn't refreshed when using alter rename to on a constraint trigger
2023-11-17 15:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
pg_dump needs SELECT privileges on irrelevant extension table
2023-03-20 16:44 UTC Jacob Champion <jchampion@timescale.com>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-03-20 17:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-03-20 18:23 UTC Jacob Champion <jchampion@timescale.com>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-03-20 22:51 UTC Jacob Champion <jchampion@timescale.com>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-06-29 16:24 UTC Jacob Champion <jchampion@timescale.com>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-07-14 07:45 UTC Akshat Jaimini <destrex271@gmail.com>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-07-14 12:04 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-07-14 22:20 UTC Jacob Champion <jchampion@timescale.com>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-08-09 23:10 UTC Jacob Champion <jchampion@timescale.com>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-10-17 20:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-10-17 21:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-10-18 20:11 UTC Stephen Frost <sfrost@snowman.net>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-10-18 20:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-10-23 18:21 UTC Jacob Champion <champion.p@gmail.com>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-10-23 18:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-11-09 19:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-11-10 20:48 UTC Jacob Champion <champion.p@gmail.com>
` Re: pg_dump needs SELECT privileges on irrelevant extension table
2023-11-15 19:59 UTC Jacob Champion <champion.p@gmail.com>
[18+ messages in thread]
LIMIT clause extremely slow
2023-11-15 16:46 UTC Melzer Kassensysteme <office@melzer-kassen.com>
` Re: LIMIT clause extremely slow
2023-11-15 17:48 UTC Christophe Pettus <xof@thebuild.com>
` Re: LIMIT clause extremely slow
2023-11-15 18:08 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[3+ messages in thread]
BUG #18199: 'Release' file not available in apt.postgresql.org/pub/repos/apt bionic-pgdg
2023-11-15 11:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18199: 'Release' file not available in apt.postgresql.org/pub/repos/apt bionic-pgdg
2023-11-15 11:46 UTC Christoph Berg <myon@debian.org>
[2+ messages in thread]
BUG #18195: PL/pgSQL: invalid syntax allowed in SELECT INTO statement
2023-11-14 13:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18195: PL/pgSQL: invalid syntax allowed in SELECT INTO statement
2023-11-14 15:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18195: PL/pgSQL: invalid syntax allowed in SELECT INTO statement
2023-11-14 15:52 UTC Pavel Stehule <pavel.stehule@gmail.com>
` RE: BUG #18195: PL/pgSQL: invalid syntax allowed in SELECT INTO statement
2023-11-15 07:22 UTC Pavel Kulakov <paul.kulakov@systematica.ru>
` Re: BUG #18195: PL/pgSQL: invalid syntax allowed in SELECT INTO statement
2023-11-15 07:33 UTC Pavel Stehule <pavel.stehule@gmail.com>
` RE: BUG #18195: PL/pgSQL: invalid syntax allowed in SELECT INTO statement
2023-11-15 07:38 UTC Pavel Kulakov <paul.kulakov@systematica.ru>
` RE: BUG #18195: PL/pgSQL: invalid syntax allowed in SELECT INTO statement
2023-11-15 07:47 UTC Pavel Kulakov <paul.kulakov@systematica.ru>
` Re: BUG #18195: PL/pgSQL: invalid syntax allowed in SELECT INTO statement
2023-11-15 07:52 UTC Pavel Stehule <pavel.stehule@gmail.com>
[8+ messages in thread]
BUG #18194: Missing install instructions
2023-11-13 20:30 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18194: Missing install instructions
2023-11-13 21:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18194: Missing install instructions
2023-11-13 21:10 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18194: Missing install instructions
2023-11-14 15:06 UTC John Pace <johnpace95@mail.de>
[4+ messages in thread]
BUG #18179: Cluster History Error
2023-11-02 09:59 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18179: Cluster History Error
2023-11-06 04:54 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18179: Cluster History Error
2023-11-13 18:00 UTC Abdullah Ergin <abdullaherginwork@gmail.com>
` Re: BUG #18179: Cluster History Error
2023-11-13 19:05 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18179: Cluster History Error
2023-11-13 19:42 UTC Abdullah Ergin <abdullaherginwork@gmail.com>
` Re: BUG #18179: Cluster History Error
2023-11-13 20:13 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18179: Cluster History Error
2023-11-13 21:04 UTC Abdullah Ergin <abdullaherginwork@gmail.com>
` Re: BUG #18179: Cluster History Error
2023-11-14 04:18 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[8+ messages in thread]
BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly
2018-04-25 00:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly
2022-08-03 18:02 UTC Alex Malek <magicagent@gmail.com>
` Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly
2023-10-28 19:42 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly
2023-10-28 20:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly
2023-10-28 21:20 UTC Pavel Borisov <pashkin.elfe@gmail.com>
` Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly
2023-10-28 23:34 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly
2023-10-28 23:39 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly
2023-10-29 15:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly
2023-10-30 13:09 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly
2023-10-30 15:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly
2023-10-30 16:00 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly
2023-10-30 16:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #15172: Postgresql ts_headline with <-> operator does not highlight text properly
2023-11-13 21:36 UTC Bruce Momjian <bruce@momjian.us>
[13+ messages in thread]
Wrong result for comparing ROW(...) with IS NOT NULL
2020-11-05 12:32 UTC Wolfgang Walther <walther@technowledgy.de>
` Re: Wrong result for comparing ROW(...) with IS NOT NULL
2020-11-05 13:14 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Wrong result for comparing ROW(...) with IS NOT NULL
2020-11-05 13:40 UTC Wolfgang Walther <walther@technowledgy.de>
` Re: Wrong result for comparing ROW(...) with IS NOT NULL
2020-11-05 13:48 UTC Pavel Borisov <pashkin.elfe@gmail.com>
` Re: Wrong result for comparing ROW(...) with IS NOT NULL
2020-11-05 14:09 UTC Wolfgang Walther <walther@technowledgy.de>
` Re: Wrong result for comparing ROW(...) with IS NOT NULL
2020-11-05 15:06 UTC Wolfgang Walther <walther@technowledgy.de>
` Re: Wrong result for comparing ROW(...) with IS NOT NULL
2020-11-05 17:43 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Wrong result for comparing ROW(...) with IS NOT NULL
2023-11-01 23:38 UTC Bruce Momjian <bruce@momjian.us>
` Re: Wrong result for comparing ROW(...) with IS NOT NULL
2023-11-13 20:21 UTC Bruce Momjian <bruce@momjian.us>
[9+ messages in thread]
BUG #18193: CVE-2019-9193
2023-11-13 06:30 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18193: CVE-2019-9193
2023-11-13 12:17 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: BUG #18193: CVE-2019-9193
2023-11-13 15:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18193: CVE-2019-9193
2023-11-13 15:30 UTC David G. Johnston <david.g.johnston@gmail.com>
[4+ messages in thread]
Bug with GIN index over JSONB data: "ERROR: buffer 10112 is not owned by resource owner"
2023-11-10 01:44 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Bug with GIN index over JSONB data: "ERROR: buffer 10112 is not owned by resource owner"
2023-11-10 03:42 UTC Junwang Zhao <zhjwpku@gmail.com>
` Re: Bug with GIN index over JSONB data: "ERROR: buffer 10112 is not owned by resource owner"
2023-11-10 04:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Bug with GIN index over JSONB data: "ERROR: buffer 10112 is not owned by resource owner"
2023-11-13 02:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #18190: PL/pgSQL does not document comparison operations on RECORD (or ROW) types
2023-11-10 19:47 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18190: PL/pgSQL does not document comparison operations on RECORD (or ROW) types
2023-11-12 01:13 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18190: PL/pgSQL does not document comparison operations on RECORD (or ROW) types
2023-11-12 15:22 UTC Karl O. Pinc <kop@karlpinc.com>
` Re: BUG #18190: PL/pgSQL does not document comparison operations on RECORD (or ROW) types
2023-11-12 15:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
AW: BUG #18189: Value partitioned tables: Upd ERROR: more than one row returned by a subquery used as an expression
2023-11-11 08:54 UTC Hans Buschmann <buschmann@nidsa.net>
` Re: AW: BUG #18189: Value partitioned tables: Upd ERROR: more than one row returned by a subquery used as an expression
2023-11-11 23:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18189: Value partitioned tables: Upd ERROR: more than one row returned by a subquery used as an expression
2023-11-10 11:07 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18189: Value partitioned tables: Upd ERROR: more than one row returned by a subquery used as an expression
2023-11-10 15:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18188: wrong varnullingrels
2023-11-09 20:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18188: wrong varnullingrels
2023-11-10 15:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Issues Encountered with PostgreSQL 16.1 RPM on EL8/EL9
2023-11-10 08:02 UTC rh@vonng.com
BUG #18184: ERROR: wrong varnullingrels (b) (expected (b 3)) for Var 2/2
2023-11-06 12:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18184: ERROR: wrong varnullingrels (b) (expected (b 3)) for Var 2/2
2023-11-07 03:06 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18184: ERROR: wrong varnullingrels (b) (expected (b 3)) for Var 2/2
2023-11-09 20:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
Segfault when running postgres inside kubernetes with huge pages
2023-11-07 17:41 UTC Siegfried Kiermayer <sicaine@gmail.com>
` Re: Segfault when running postgres inside kubernetes with huge pages
2023-11-08 14:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Segfault when running postgres inside kubernetes with huge pages
2023-11-08 15:03 UTC Siegfried Kiermayer <sicaine@gmail.com>
` Re: Segfault when running postgres inside kubernetes with huge pages
2023-11-09 01:28 UTC Andres Freund <andres@anarazel.de>
[4+ messages in thread]
ALTER TABLE results in "could not find cast from 3904 to 3831"
2019-11-16 22:46 UTC Manuel Rigger <rigger.manuel@gmail.com>
` Re: ALTER TABLE results in "could not find cast from 3904 to 3831"
2019-11-16 23:56 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: ALTER TABLE results in "could not find cast from 3904 to 3831"
2023-11-08 18:58 UTC Bruce Momjian <bruce@momjian.us>
[3+ messages in thread]
BUG #17552: pg_stat_statements tracks internal FK check queries when COPY used to load data
2022-07-17 19:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17552: pg_stat_statements tracks internal FK check queries when COPY used to load data
2022-07-18 10:19 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #17552: pg_stat_statements tracks internal FK check queries when COPY used to load data
2023-03-22 12:21 UTC Sergei Kornilov <sk@zsrv.org>
` Re: BUG #17552: pg_stat_statements tracks internal FK check queries when COPY used to load data
2023-07-16 15:19 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #17552: pg_stat_statements tracks internal FK check queries when COPY used to load data
2023-07-18 16:19 UTC Sergei Kornilov <sk@zsrv.org>
` Re: BUG #17552: pg_stat_statements tracks internal FK check queries when COPY used to load data
2023-11-01 17:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17552: pg_stat_statements tracks internal FK check queries when COPY used to load data
2023-11-01 21:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re:BUG #17552: pg_stat_statements tracks internal FK check queries when COPY used to load data
2023-11-07 20:23 UTC Sergei Kornilov <sk@zsrv.org>
` Re: BUG #17552: pg_stat_statements tracks internal FK check queries when COPY used to load data
2023-11-08 17:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
[9+ messages in thread]
BUG #18177: certain queries under certain contexts take multiple orders of magnitude longer compared to v10
2023-11-01 23:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18177: certain queries under certain contexts take multiple orders of magnitude longer compared to v10
2023-11-02 10:45 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18177: certain queries under certain contexts take multiple orders of magnitude longer compared to v10
2023-11-02 20:04 UTC Robert Leach <rleach@princeton.edu>
` Re: BUG #18177: certain queries under certain contexts take multiple orders of magnitude longer compared to v10
2023-11-02 22:00 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: BUG #18177: certain queries under certain contexts take multiple orders of magnitude longer compared to v10
2023-11-03 00:23 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18177: certain queries under certain contexts take multiple orders of magnitude longer compared to v10
2023-11-03 14:45 UTC Robert Leach <rleach@princeton.edu>
` Re: BUG #18177: certain queries under certain contexts take multiple orders of magnitude longer compared to v10
2023-11-03 17:49 UTC Robert Leach <rleach@princeton.edu>
` Re: BUG #18177: certain queries under certain contexts take multiple orders of magnitude longer compared to v10
2023-11-06 18:22 UTC Robert Leach <rleach@princeton.edu>
` Re: BUG #18177: certain queries under certain contexts take multiple orders of magnitude longer compared to v10
2023-11-06 22:38 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18177: certain queries under certain contexts take multiple orders of magnitude longer compared to v10
2023-11-07 16:43 UTC Robert Leach <rleach@princeton.edu>
` Re: BUG #18177: certain queries under certain contexts take multiple orders of magnitude longer compared to v10
2023-11-08 16:03 UTC Robert Leach <rleach@princeton.edu>
[11+ messages in thread]
Windows compatibility
2023-11-07 20:30 UTC Mohamed Magdy <mohamed.magdy@emsegypt.net>
` Re: Windows compatibility
2023-11-08 12:27 UTC Daniel Gustafsson <daniel@yesql.se>
[2+ messages in thread]
BUG #18185: Error when calling whoami at the beginning of the installation
2023-11-06 15:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18185: Error when calling whoami at the beginning of the installation
2023-11-07 07:32 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18185: Error when calling whoami at the beginning of the installation
2023-11-08 07:02 UTC Manika Singhal <manika.singhal@enterprisedb.com>
[3+ messages in thread]
BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25
2023-06-11 15:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25
2023-06-11 17:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25
2023-06-16 02:18 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25
2023-06-16 02:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25
2023-09-26 07:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25
2023-10-23 20:58 UTC shihao zhong <zhong950419@gmail.com>
` Re: BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25
2023-10-24 13:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17969: Assert failed in bloom_init() when false_positive_rate = 0.25
2023-11-08 05:18 UTC Michael Paquier <michael@paquier.xyz>
[8+ 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