pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18497: Heap-use-after-free in plpgsql
2024-06-06 09:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18497: Heap-use-after-free in plpgsql
2024-06-12 23:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18506: Memory Leak on wrong INNER JOINs
2024-06-12 13:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18506: Memory Leak on wrong INNER JOINs
2024-06-12 14:41 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18506: Memory Leak on wrong INNER JOINs
2024-06-12 15:09 UTC GoutisD <gts.dmtr@gmail.com>
[3+ messages in thread]
Issue Report: Unique Constraint Violation Error in PostgreSQL
2024-06-12 08:55 UTC sing_hijo@outlook.com <sing_hijo@outlook.com>
` Re: Issue Report: Unique Constraint Violation Error in PostgreSQL
2024-06-12 09:59 UTC Muhammad Ikram <mmikram@gmail.com>
` Re: Issue Report: Unique Constraint Violation Error in PostgreSQL
2024-06-12 11:56 UTC Francisco Olarte <folarte@peoplecall.com>
[3+ messages in thread]
BUG #18334: Segfault when running a query with parallel workers
2024-02-05 10:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18334: Segfault when running a query with parallel workers
2024-02-06 01:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18334: Segfault when running a query with parallel workers
2024-02-06 11:30 UTC Marcin Barczyński <mba.ogolny@gmail.com>
` Re: BUG #18334: Segfault when running a query with parallel workers
2024-02-11 21:30 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18334: Segfault when running a query with parallel workers
2024-05-23 11:59 UTC Marcin Barczyński <mba.ogolny@gmail.com>
` Re: BUG #18334: Segfault when running a query with parallel workers
2024-05-24 00:45 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18334: Segfault when running a query with parallel workers
2024-05-24 01:32 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18334: Segfault when running a query with parallel workers
2024-05-24 08:26 UTC Marcin Barczyński <mba.ogolny@gmail.com>
` Re: BUG #18334: Segfault when running a query with parallel workers
2024-05-29 13:32 UTC Marcin Barczyński <mba.ogolny@gmail.com>
` Re: BUG #18334: Segfault when running a query with parallel workers
2024-06-12 09:53 UTC Marcin Barczyński <mba.ogolny@gmail.com>
[10+ messages in thread]
BUG #18502: Upsert on view returns 42P10 error when condition is an expression
2024-06-11 09:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18502: Upsert on view returns 42P10 error when condition is an expression
2024-06-11 20:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18502: Upsert on view returns 42P10 error when condition is an expression
2024-06-12 02:18 UTC David G. Johnston <david.g.johnston@gmail.com>
[3+ messages in thread]
回复: BUG #18502: Upsert on view returns 42P10 error when condition is an expression
2024-06-12 02:11 UTC 王 海 <michael.wanghai.a@outlook.com>
BUG #18505: while installation of postgresql ,getting warning by selecting postresql 16 on port 5432
2024-06-11 20:22 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18504: More than one row with the same Primary Key
2024-06-11 14:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18504: More than one row with the same Primary Key
2024-06-11 19:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18501: haproxy-3.0.0 not signed
2024-06-10 15:49 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18391: not able to create a new cluster using init db on rocky linux.We are forced to download version 1 3
2024-03-13 11:18 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18391: not able to create a new cluster using init db on rocky linux.We are forced to download version 1 3
2024-03-13 13:00 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18391: not able to create a new cluster using init db on rocky linux.We are forced to download version 1 3
2024-06-10 09:01 UTC HAQ LATIF <haq963@hotmail.com>
` Re: BUG #18391: not able to create a new cluster using init db on rocky linux.We are forced to download version 1 3
2024-06-10 09:26 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[4+ messages in thread]
BUG #18333: Postgres is crashing if we have special character in the query
2024-02-05 10:30 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18333: Postgres is crashing if we have special character in the query
2024-02-06 01:32 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18333: Postgres is crashing if we have special character in the query
2024-05-07 12:49 UTC Sujeet Swaminath <sujeet.cha@gmail.com>
` Re: BUG #18333: Postgres is crashing if we have special character in the query
2024-06-10 07:53 UTC Michael Paquier <michael@paquier.xyz>
[4+ messages in thread]
BUG: value in information_schema.parameters.parameter_default is always NULL for roles t
2024-06-09 10:44 UTC Vedran Bilopavlović <vbilopav@gmail.com>
` Re: BUG: value in information_schema.parameters.parameter_default is always NULL for roles t
2024-06-09 17:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18498: Locking a table from a trigger (with using two sessions) causes a deadlock: the bug or the feature?
2024-06-07 07:55 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18498: Locking a table from a trigger (with using two sessions) causes a deadlock: the bug or the feature?
2024-06-07 08:47 UTC Dmitry Koval <d.koval@postgrespro.ru>
` Re: BUG #18498: Locking a table from a trigger (with using two sessions) causes a deadlock: the bug or the feature?
2024-06-07 08:58 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18498: Locking a table from a trigger (with using two sessions) causes a deadlock: the bug or the feature?
2024-06-07 09:02 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18498: Locking a table from a trigger (with using two sessions) causes a deadlock: the bug or the feature?
2024-06-07 09:45 UTC Dmitry Koval <d.koval@postgrespro.ru>
` RE: [EXTERNAL] BUG #18498: Locking a table from a trigger (with using two sessions) causes a deadlock: the bug or the feature?
2024-06-07 17:32 UTC Wetmore, Matthew (CTR) <Matthew.Wetmore@evernorth.com>
[6+ messages in thread]
BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-15 07:03 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-15 09:41 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-16 04:02 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-16 09:02 UTC Önder Kalacı <onderkalaci@gmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-16 09:11 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-16 09:54 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-16 09:56 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-16 15:27 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-16 16:15 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-16 16:29 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-16 16:47 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-16 16:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-17 02:45 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-20 09:08 UTC Önder Kalacı <onderkalaci@gmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-21 10:32 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-23 06:54 UTC Önder Kalacı <onderkalaci@gmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-23 14:30 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-24 08:32 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-28 14:20 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-30 07:15 UTC Önder Kalacı <onderkalaci@gmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-30 12:56 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-30 13:08 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-31 01:12 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-31 07:22 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-05-31 09:50 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-06-05 01:08 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-06-05 01:21 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
` Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
2024-06-07 09:10 UTC Etsuro Fujita <etsuro.fujita@gmail.com>
[28+ messages in thread]
[PATCH v2 2/2] Fix partition pruning setup during DETACH CONCURRENTLY
2024-06-07 08:12 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` [PATCH v3] Fix partition pruning setup during DETACH CONCURRENTLY
2024-06-07 08:12 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` [PATCH v4] Fix partition pruning setup during DETACH CONCURRENTLY
2024-06-07 08:12 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[3+ messages in thread]
BUG #18496: Strange Handling for Circular Views and Permissions in PostgreSQL
2024-06-06 07:12 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18496: Strange Handling for Circular Views and Permissions in PostgreSQL
2024-06-06 16:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Error of reinstallatio
2024-06-03 14:26 UTC Chant Guo <yuzhongqiyuan@gmail.com>
` Re: Error of reinstallatio
2024-06-04 06:56 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` Re: Error of reinstallatio
2024-06-06 13:37 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
[3+ messages in thread]
BUG #18473: Problems deployment postgresql for windows
2024-05-21 11:44 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18473: Problems deployment postgresql for windows
2024-06-05 02:17 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` Re: BUG #18473: Problems deployment postgresql for windows
2024-06-06 13:36 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
[3+ messages in thread]
BUG #18477: A specific SQL query with "ORDER BY ... NULLS FIRST" is performing poorly if an ordering column is n
2024-05-23 17:34 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18477: A specific SQL query with "ORDER BY ... NULLS FIRST" is performing poorly if an ordering column is n
2024-05-23 18:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18477: A specific SQL query with "ORDER BY ... NULLS FIRST" is performing poorly if an ordering column is n
2024-05-24 08:34 UTC Alexander Alexander <alexander.berezin3000@gmail.com>
` Re: BUG #18477: A specific SQL query with "ORDER BY ... NULLS FIRST" is performing poorly if an ordering column is n
2024-05-24 10:03 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18477: A specific SQL query with "ORDER BY ... NULLS FIRST" is performing poorly if an ordering column is n
2024-06-06 03:29 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18477: A specific SQL query with "ORDER BY ... NULLS FIRST" is performing poorly if an ordering column is n
2024-06-06 03:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18477: A specific SQL query with "ORDER BY ... NULLS FIRST" is performing poorly if an ordering column is n
2024-06-06 05:04 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18477: A specific SQL query with "ORDER BY ... NULLS FIRST" is performing poorly if an ordering column is n
2024-06-06 08:10 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18477: A specific SQL query with "ORDER BY ... NULLS FIRST" is performing poorly if an ordering column is n
2024-06-06 08:27 UTC David Rowley <dgrowleyml@gmail.com>
[9+ messages in thread]
BUG #18494: hstore data type not recognized by Npgsql in PostgreSQL 16.3
2024-06-04 14:46 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18494: hstore data type not recognized by Npgsql in PostgreSQL 16.3
2024-06-04 16:09 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: BUG #18494: hstore data type not recognized by Npgsql in PostgreSQL 16.3
2024-06-06 07:20 UTC Baran Kurtboğan <barankurtbogan@gmail.com>
[3+ messages in thread]
BUG #17947: Combination of replslots pgstat issues causes error/assertion failure
2023-05-26 11:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17947: Combination of replslots pgstat issues causes error/assertion failure
2023-05-31 23:42 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17947: Combination of replslots pgstat issues causes error/assertion failure
2023-06-02 21:34 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17947: Combination of replslots pgstat issues causes error/assertion failure
2024-05-05 18:37 UTC Andres Freund <andres@anarazel.de>
` RE: BUG #17947: Combination of replslots pgstat issues causes error/assertion failure
2024-06-02 21:31 UTC Floris Van Nee <florisvannee@Optiver.com>
` Re: BUG #17947: Combination of replslots pgstat issues causes error/assertion failure
2024-06-04 05:25 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17947: Combination of replslots pgstat issues causes error/assertion failure
2024-06-05 06:23 UTC Michael Paquier <michael@paquier.xyz>
` RE: BUG #17947: Combination of replslots pgstat issues causes error/assertion failure
2024-06-05 10:24 UTC Floris Van Nee <florisvannee@Optiver.com>
` Re: BUG #17947: Combination of replslots pgstat issues causes error/assertion failure
2024-06-05 23:51 UTC Michael Paquier <michael@paquier.xyz>
[9+ messages in thread]
BUG #18495: invalid type mapping for timestamptz from call of: getMetaData and then geColumns on PgConnection.
2024-06-05 13:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18495: invalid type mapping for timestamptz from call of: getMetaData and then geColumns on PgConnection.
2024-06-05 16:08 UTC Erik Wienhold <ewie@ewie.name>
[2+ messages in thread]
Minor update on pg_hba documentation
2024-06-04 15:22 UTC SAS <sas.postgresql@gmail.com>
` Re: Minor update on pg_hba documentation
2024-06-05 03:30 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Minor update on pg_hba documentation
2024-06-05 06:33 UTC Michael Paquier <michael@paquier.xyz>
` Re: Minor update on pg_hba documentation
2024-06-05 11:19 UTC Michael Paquier <michael@paquier.xyz>
[4+ messages in thread]
BUG #18463: Possible bug in stored procedures with polymorphic OUT parameters
2024-05-14 06:45 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18463: Possible bug in stored procedures with polymorphic OUT parameters
2024-05-14 15:18 UTC Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #18463: Possible bug in stored procedures with polymorphic OUT parameters
2024-05-14 17:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18463: Possible bug in stored procedures with polymorphic OUT parameters
2024-05-14 19:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18463: Possible bug in stored procedures with polymorphic OUT parameters
2024-05-15 00:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18463: Possible bug in stored procedures with polymorphic OUT parameters
2024-05-15 14:35 UTC Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #18463: Possible bug in stored procedures with polymorphic OUT parameters
2024-05-15 17:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18463: Possible bug in stored procedures with polymorphic OUT parameters
2024-06-04 14:22 UTC Andrew Bille <andrewbille@gmail.com>
` Re: BUG #18463: Possible bug in stored procedures with polymorphic OUT parameters
2024-06-04 17:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18463: Possible bug in stored procedures with polymorphic OUT parameters
2024-06-04 21:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
[10+ messages in thread]
intarray bigint support
2024-06-04 20:56 UTC Casey & Gina <cg@osss.net>
[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