pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #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]
(no subject)
2017-02-09 02:28 UTC 片本 亘祐（ユニークビジョン） <katamoto_kosuke@uniquevision.co.jp>
` Re:
2017-02-09 02:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` BUG #18186: Question around integration
2023-11-07 13:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18186: Question around integration
2023-11-07 20:59 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #18186: Question around integration
2023-11-07 21:01 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18186: Question around integration
2023-11-07 21:38 UTC Andrew Dunstan <andrew@dunslane.net>
[6+ messages in thread]
BUG #18183: Unable to grant similar roles after changing user from No inheritance to Inheritance.
2023-11-06 10:30 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18183: Unable to grant similar roles after changing user from No inheritance to Inheritance.
2023-11-06 14:11 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18183: Unable to grant similar roles after changing user from No inheritance to Inheritance.
2023-11-06 14:21 UTC David G. Johnston <david.g.johnston@gmail.com>
[3+ messages in thread]
BUG #18182: apt distribution is missing for Bionic
2023-11-06 09:53 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18182: apt distribution is missing for Bionic
2023-11-06 10:06 UTC Magnus Hagander <magnus@hagander.net>
[2+ messages in thread]
BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-26 14:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-26 15:21 UTC Vik Fearing <vik@postgresfriends.org>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-26 17:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-26 17:35 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-26 17:36 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-27 06:31 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-27 08:17 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-27 09:07 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-27 11:00 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-27 14:10 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-27 14:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-27 21:12 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-28 06:59 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-28 07:31 UTC Vik Fearing <vik@postgresfriends.org>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-28 10:10 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-28 11:00 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-28 22:39 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-29 15:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-30 02:01 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-30 02:24 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-30 02:43 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-30 02:47 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-30 06:24 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-31 05:05 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-31 07:37 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-31 08:05 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-31 08:21 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-10-31 08:46 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-11-01 03:55 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-11-01 10:29 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-11-01 22:29 UTC Alexander Korotkov <aekorotkov@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-11-02 02:10 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-11-06 07:26 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18170: Unexpected error: no relation entry for relid 3
2023-11-06 08:04 UTC Alexander Korotkov <aekorotkov@gmail.com>
[34+ messages in thread]
COPY TO CSV produces data that is incompatible/unsafe for \COPY FROM CSV
2022-06-15 12:16 UTC Svante Richter <pgsql-bugs@richter.id>
` Re: COPY TO CSV produces data that is incompatible/unsafe for \COPY FROM CSV
2022-08-09 20:48 UTC Svante Richter <pgsql-bugs@richter.id>
` Re: COPY TO CSV produces data that is incompatible/unsafe for \COPY FROM CSV
2022-08-14 07:00 UTC Noah Misch <noah@leadboat.com>
` Re: COPY TO CSV produces data that is incompatible/unsafe for \COPY FROM CSV
2022-08-14 14:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: COPY TO CSV produces data that is incompatible/unsafe for \COPY FROM CSV
2022-08-16 15:26 UTC Bruce Momjian <bruce@momjian.us>
` Re: COPY TO CSV produces data that is incompatible/unsafe for \COPY FROM CSV
2022-08-17 05:26 UTC Noah Misch <noah@leadboat.com>
` Re: COPY TO CSV produces data that is incompatible/unsafe for \COPY FROM CSV
2023-10-28 15:38 UTC Bruce Momjian <bruce@momjian.us>
` Re: COPY TO CSV produces data that is incompatible/unsafe for \COPY FROM CSV
2023-11-03 17:58 UTC Bruce Momjian <bruce@momjian.us>
[8+ messages in thread]
BUG #18178: New Restriction on "ON SELECT" rules on tables
2023-11-01 23:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18178: New Restriction on "ON SELECT" rules on tables
2023-11-02 09:44 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18178: New Restriction on "ON SELECT" rules on tables
2023-11-02 10:40 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18178: New Restriction on "ON SELECT" rules on tables
2023-11-02 14:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18178: New Restriction on "ON SELECT" rules on tables
2023-11-03 10:44 UTC Joshua Uyehara <joshua.uyehara@gmail.com>
` Re: BUG #18178: New Restriction on "ON SELECT" rules on tables
2023-11-03 15:21 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18178: New Restriction on "ON SELECT" rules on tables
2023-11-03 15:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18178: New Restriction on "ON SELECT" rules on tables
2023-11-03 15:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
[8+ messages in thread]
Installation problem with application stack builder
2023-11-03 14:27 UTC Gazel Alvarado Ivan <IGazel@ice.go.cr>
BUG #18180: Maybe a bug? repomd.xml signature could not be verified for pgdg-common
2023-11-02 17:01 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18167: cannot create partitioned tables when default_tablespace is set
2023-10-24 09:42 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18167: cannot create partitioned tables when default_tablespace is set
2023-10-25 07:45 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18167: cannot create partitioned tables when default_tablespace is set
2023-10-25 09:58 UTC tender wang <tndrwang@gmail.com>
` Re: BUG #18167: cannot create partitioned tables when default_tablespace is set
2023-11-02 12:50 UTC Marius RAICU <mariusraicu@laposte.net>
[4+ messages in thread]
BUG #18173: ERROR: could not identify a comparison function for type unknown
2023-10-30 13:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18173: ERROR: could not identify a comparison function for type unknown
2023-10-31 11:10 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18173: ERROR: could not identify a comparison function for type unknown
2023-10-31 14:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18173: ERROR: could not identify a comparison function for type unknown
2023-11-01 07:44 UTC 下雨天 <409800246@qq.com>
[4+ messages in thread]
回复： BUG #18173: ERROR: could not identify a comparison function for type unknown
2023-10-31 12:19 UTC 下雨天 <409800246@qq.com>
BUG #18172: High memory usage in tSRF function context
2023-10-27 11:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18172: High memory usage in tSRF function context
2023-10-28 03:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re:BUG #18172: High memory usage in tSRF function context
2023-10-28 07:56 UTC Sergei Kornilov <sk@zsrv.org>
` Re: BUG #18172: High memory usage in tSRF function context
2023-10-28 18:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re:BUG #18172: High memory usage in tSRF function context
2023-10-28 18:47 UTC Sergei Kornilov <sk@zsrv.org>
[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