pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18239: select position ('' in 'A') returns 1
2023-12-10 10:22 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18239: select position ('' in 'A') returns 1
2023-12-10 15:20 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18239: select position ('' in 'A') returns 1
2023-12-10 16:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #18237: C:\Users\админ\AppData\Local\Temp\postgresql_installer_7ddb2d40c9
2023-12-09 06:31 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18237: C:\Users\админ\AppData\Local\Temp\postgresql_installer_7ddb2d40c9
2023-12-09 06:35 UTC Омар Айбек <omar-aybek@mail.ru>
[2+ messages in thread]
BUG #18234: Nested Loop joint strategy is ignored for a tiny table joined with UNION ALL of two filtered parts
2023-12-07 18:50 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18234: Nested Loop joint strategy is ignored for a tiny table joined with UNION ALL of two filtered parts
2023-12-07 21:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18234: Nested Loop joint strategy is ignored for a tiny table joined with UNION ALL of two filtered parts
2023-12-08 01:19 UTC Dmytro Astapov <dastapov@gmail.com>
` Re: BUG #18234: Nested Loop joint strategy is ignored for a tiny table joined with UNION ALL of two filtered parts
2023-12-08 15:03 UTC Dmytro Astapov <dastapov@gmail.com>
[4+ messages in thread]
BUG #18236: Backend processing a parallel query terminates badly when postmaster killed with SIGKILL
2023-12-08 05:00 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18235: Unable to install postgreSQL15 on Oracle Cloud VM
2023-12-08 04:29 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18233: coerce_type accepts NULL as pstate and can pass it to coerce_record_to_complex
2023-12-07 12:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18233: coerce_type accepts NULL as pstate and can pass it to coerce_record_to_complex
2023-12-07 14:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18232: Function pushJsonbValueScalar has not Assert(scalarVal) on WJB_KEY, WJB_VALUE and WJB_ELEM
2023-12-07 11:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18232: Function pushJsonbValueScalar has not Assert(scalarVal) on WJB_KEY, WJB_VALUE and WJB_ELEM
2023-12-07 14:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18231: String conversion function is adding special characters in Postgres 15
2023-12-07 09:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18231: String conversion function is adding special characters in Postgres 15
2023-12-07 10:51 UTC Heikki Linnakangas <hlinnaka@iki.fi>
[2+ messages in thread]
BUG #18230: Redundant comparison of a local variable 'tzp' address with a NULL value at dt_common.c
2023-12-06 04:49 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18230: Redundant comparison of a local variable 'tzp' address with a NULL value at dt_common.c
2023-12-06 13:55 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18230: Redundant comparison of a local variable 'tzp' address with a NULL value at dt_common.c
2023-12-06 14:44 UTC RekGRpth <rekgrpth@gmail.com>
` Re: BUG #18230: Redundant comparison of a local variable 'tzp' address with a NULL value at dt_common.c
2023-12-06 16:38 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18230: Redundant comparison of a local variable 'tzp' address with a NULL value at dt_common.c
2023-12-06 16:41 UTC RekGRpth <rekgrpth@gmail.com>
` Re: BUG #18230: Redundant comparison of a local variable 'tzp' address with a NULL value at dt_common.c
2023-12-06 21:01 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18230: Redundant comparison of a local variable 'tzp' address with a NULL value at dt_common.c
2023-12-07 01:51 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18230: Redundant comparison of a local variable 'tzp' address with a NULL value at dt_common.c
2023-12-07 02:28 UTC RekGRpth <rekgrpth@gmail.com>
` Re: BUG #18230: Redundant comparison of a local variable 'tzp' address with a NULL value at dt_common.c
2023-12-07 02:32 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #18230: Redundant comparison of a local variable 'tzp' address with a NULL value at dt_common.c
2023-12-07 02:39 UTC RekGRpth <rekgrpth@gmail.com>
` Re: BUG #18230: Redundant comparison of a local variable 'tzp' address with a NULL value at dt_common.c
2023-12-07 04:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
[11+ messages in thread]
BUG #18213: Standby's repeatable read isolation level transaction encountered a "nonrepeatable read" problem
2023-11-24 08:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18213: Standby's repeatable read isolation level transaction encountered a "nonrepeatable read" problem
2023-11-29 05:26 UTC zhihuifan1213@163.com
` Re: 回复： BUG #18213: Standby's repeatable read isolation level transaction encountered a "nonrepeatable read" problem
2023-11-29 07:50 UTC zhihuifan1213@163.com
` Re: BUG #18213: Standby's repeatable read isolation level transaction encountered a "nonrepeatable read" problem
2023-12-05 11:47 UTC 费长红 <feichanghong@qq.com>
` Re: BUG #18213: Standby's repeatable read isolation level transaction encountered a "nonrepeatable read" problem
2023-12-06 02:32 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
[5+ messages in thread]
BUG #18229: Multiple vacuum queries fail after upgrading to 13.10
2023-12-05 14:22 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18229: Multiple vacuum queries fail after upgrading to 13.10
2023-12-05 15:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17948: libpq seems to misbehave in a pipelining corner case
2023-05-26 17:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17948: libpq seems to misbehave in a pipelining corner case
2023-07-16 11:57 UTC Трофимов Иван <i.trofimow@yandex.ru>
` Re:BUG #17948: libpq seems to misbehave in a pipelining corner case
2023-08-05 12:03 UTC Трофимов Иван <i.trofimow@yandex.ru>
` Re: BUG #17948: libpq seems to misbehave in a pipelining corner case
2023-12-01 14:20 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17948: libpq seems to misbehave in a pipelining corner case
2023-12-02 20:56 UTC Ivan Trofimov <i.trofimow@yandex.ru>
` Re: BUG #17948: libpq seems to misbehave in a pipelining corner case
2023-12-04 18:47 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[6+ messages in thread]
BUG #15902: pgAdmin generates faulty SQL
2019-07-09 11:43 UTC PG Bug reporting form <noreply@postgresql.org>
` [PATCH v2] Fix handling of errors in libpq pipelines
2023-12-04 17:15 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[2+ messages in thread]
BUG #18225: chdb's s3 table function crashes postgresql with plpython3
2023-12-04 13:47 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18225: chdb's s3 table function crashes postgresql with plpython3
2023-12-04 14:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18222: Unexpected Error--Cannot delete from scalar
2023-12-04 05:56 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18222: Unexpected Error--Cannot delete from scalar
2023-12-04 13:50 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BUG #18222: Unexpected Error--Cannot delete from scalar
2023-12-04 14:15 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18222: Unexpected Error--Cannot delete from scalar
2023-12-04 14:21 UTC Ba Jinsheng <bajinsheng@u.nus.edu>
[4+ messages in thread]
BUG #18223: There is a confusing result where an update statement can reference itself and execute successfully.
2023-12-04 06:27 UTC PG Bug reporting form <noreply@postgresql.org>
` RE: BUG #18223: There is a confusing result where an update statement can reference itself and execute successfully.
2023-12-04 12:51 UTC Orlov Aleksej <al.orlov@cft.ru>
[2+ messages in thread]
BUG #18221: Unexpected Query Result
2023-12-02 02:47 UTC PG Bug reporting form <noreply@postgresql.org>
` Re:BUG #18221: Unexpected Query Result
2023-12-03 13:44 UTC Sergei Kornilov <sk@zsrv.org>
` Re: Re:BUG #18221: Unexpected Query Result
2023-12-04 01:17 UTC Ba Jinsheng <bajinsheng@u.nus.edu>
[3+ messages in thread]
BUG #18219: libpq does not take into consideration UNICODE define
2023-11-30 15:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18219: libpq does not take into consideration UNICODE define
2023-11-30 19:20 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18219: libpq does not take into consideration UNICODE define
2023-11-30 21:10 UTC Jan Březina <2janbrezina@gmail.com>
` Re: BUG #18219: libpq does not take into consideration UNICODE define
2023-11-30 21:20 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18219: libpq does not take into consideration UNICODE define
2023-11-30 21:21 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18219: libpq does not take into consideration UNICODE define
2023-11-30 21:50 UTC Jan Březina <2janbrezina@gmail.com>
` Re: BUG #18219: libpq does not take into consideration UNICODE define
2023-11-30 21:58 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18219: libpq does not take into consideration UNICODE define
2023-11-30 22:19 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18219: libpq does not take into consideration UNICODE define
2023-11-30 22:32 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18219: libpq does not take into consideration UNICODE define
2023-12-03 19:55 UTC Jan Březina <2janbrezina@gmail.com>
` Re: BUG #18219: libpq does not take into consideration UNICODE define
2023-12-03 22:20 UTC Thomas Munro <thomas.munro@gmail.com>
` RE: BUG #18219: libpq does not take into consideration UNICODE define
2023-12-03 22:31 UTC Jeff Laing <Jeff.Laing@synchronoss.com>
[12+ messages in thread]
BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2022-07-05 22:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2022-07-06 22:07 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2022-07-07 00:23 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2022-07-07 00:46 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2022-07-07 00:46 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2022-07-07 01:54 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2022-07-07 03:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2022-07-07 03:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2022-07-07 03:31 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2022-07-07 03:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2022-07-07 04:36 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2022-07-07 18:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2023-07-05 23:55 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2023-07-06 09:26 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2023-07-07 07:02 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2023-07-10 02:14 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2023-07-10 06:39 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2023-07-26 03:17 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2023-09-26 13:42 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2023-09-28 03:22 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2023-09-28 03:51 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2023-10-08 08:26 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2023-10-24 04:25 UTC Andrei Lepikhov <a.lepikhov@postgrespro.ru>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2023-11-01 02:20 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2023-11-29 00:48 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17540: Prepared statement: PG switches to a generic query plan which is consistently much slower
2023-12-01 10:07 UTC Richard Guo <guofenglinux@gmail.com>
[26+ messages in thread]
BUG #18220: drop database in anytime
2023-12-01 03:15 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18198: Constantly getting errors
2023-11-15 09:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18198: Constantly getting errors
2023-11-30 07:13 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
` Re: BUG #18198: Constantly getting errors
2023-11-30 13:36 UTC Şeyma Alkan <symalkn@gmail.com>
[3+ messages in thread]
BUG #18218: NOT LIKE ANY returns same result as LIKE ANY when array items are wrapped into E''
2023-11-30 10:54 UTC PG Bug reporting form <noreply@postgresql.org>
` RE: BUG #18218: NOT LIKE ANY returns same result as LIKE ANY when array items are wrapped into E''
2023-11-30 12:50 UTC Orlov Aleksej <al.orlov@cft.ru>
` Re: BUG #18218: NOT LIKE ANY returns same result as LIKE ANY when array items are wrapped into E''
2023-11-30 13:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18218: NOT LIKE ANY returns same result as LIKE ANY when array items are wrapped into E''
2023-11-30 13:20 UTC Bauyrzhan Sakhariyev <baurzhansahariev@gmail.com>
[4+ messages in thread]
(no subject)
2017-01-27 14:16 UTC sellier nicolas <nicosellier@yahoo.fr>
` BUG #18201: POSTGRESQL 16 - Failed to initialise the database cluster with initdb
2023-11-16 09:27 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18201: POSTGRESQL 16 - Failed to initialise the database cluster with initdb
2023-11-30 07:15 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
[3+ messages in thread]
Re:Could not read from file "pg_subtrans/00F5" at offset 122880: Success.
2023-11-27 11:50 UTC Sri Mrudula Attili <sri@ebi.ac.uk>
` Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.
2023-11-27 16:12 UTC Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.
2023-11-27 18:58 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.
2023-11-28 08:54 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.
2023-11-28 14:57 UTC Sri Mrudula Attili <sri@ebi.ac.uk>
` Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.
2023-11-29 17:20 UTC Sri Mrudula Attili <sri@ebi.ac.uk>
` Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.
2023-11-29 17:29 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.
2023-11-29 20:24 UTC Ron Johnson <ronljohnsonjr@gmail.com>
` Re: Could not read from file "pg_subtrans/00F5" at offset 122880: Success.
2023-11-30 00:39 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
[9+ messages in thread]
BUG #18217: ALTER TABLE IF EXISTS not being honored with DROP CONSTRAINT IF EXISTS
2023-11-29 14:59 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18217: ALTER TABLE IF EXISTS not being honored with DROP CONSTRAINT IF EXISTS
2023-11-29 16:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ 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