pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17464: Domain type. If the value field(CREATE DOMAIN) is set to null, errors cannot be intercepted.
2022-04-12 12:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17464: Domain type. If the value field(CREATE DOMAIN) is set to null, errors cannot be intercepted.
2022-04-12 14:27 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17464: Domain type. If the value field(CREATE DOMAIN) is set to null, errors cannot be intercepted.
2022-04-12 14:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
Docs for psql regarding default database name are incorrect
2022-03-14 00:15 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Docs for psql regarding default database name are incorrect
2022-04-12 02:46 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #17457: pg_rewind fatal failure when $PGDATA/log is a soft-link
2022-04-06 21:08 UTC PG Bug reporting form <noreply@postgresql.org>
Wrong behaviour of array comparison when arrays contain nulls
2022-04-06 12:22 UTC Lukas Eder <lukas.eder@gmail.com>
` Re: Wrong behaviour of array comparison when arrays contain nulls
2022-04-06 13:13 UTC Lukas Eder <lukas.eder@gmail.com>
` Re: Wrong behaviour of array comparison when arrays contain nulls
2022-04-06 13:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #17456: pg_dump creates dump that does not fully respect operator schema location
2022-04-05 15:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17456: pg_dump creates dump that does not fully respect operator schema location
2022-04-05 16:05 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17456: pg_dump creates dump that does not fully respect operator schema location
2022-04-05 17:09 UTC Andrew Grossman <agrossman@gmail.com>
[3+ messages in thread]
SAVEPOINT issue
2022-04-05 14:21 UTC archana srinivas <archanasrinivas107@gmail.com>
` Re: SAVEPOINT issue
2022-04-05 15:48 UTC Bruce Momjian <bruce@momjian.us>
[2+ messages in thread]
a code question
2022-04-05 05:41 UTC qiumingcheng <qiumingcheng@aliyun.com>
` Re: a code question
2022-04-05 07:14 UTC David Rowley <dgrowleyml@gmail.com>
[2+ messages in thread]
AW: BUG #17393: Delete database after recovery with point-in-time is still missing datafiles
2022-03-04 07:09 UTC Lorenz, Christopher <Christopher.Lorenz@ZIT-BB.Brandenburg.de>
` AW: BUG #17393: Delete database after recovery with point-in-time is still missing datafiles
2022-03-30 11:49 UTC Lorenz, Christopher <Christopher.Lorenz@ZIT-BB.Brandenburg.de>
` AW: BUG #17393: Delete database after recovery with point-in-time is still missing datafiles
2022-04-04 07:00 UTC Lorenz, Christopher <Christopher.Lorenz@ZIT-BB.Brandenburg.de>
[3+ messages in thread]
BUG #17454: Using psql without ipv4 address,the inet_server_port do not return PORT.
2022-04-02 01:15 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17454: Using psql without ipv4 address,the inet_server_port do not return PORT.
2022-04-02 15:07 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17454: Using psql without ipv4 address,the inet_server_port do not return PORT.
2022-04-03 01:40 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17454: Using psql without ipv4 address,the inet_server_port do not return PORT.
2022-04-03 15:35 UTC Francisco Olarte <folarte@peoplecall.com>
` Re: BUG #17454: Using psql without ipv4 address,the inet_server_port do not return PORT.
2022-04-03 15:50 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17454: Using psql without ipv4 address,the inet_server_port do not return PORT.
2022-04-03 16:28 UTC Francisco Olarte <folarte@peoplecall.com>
` Re: BUG #17454: Using psql without ipv4 address,the inet_server_port do not return PORT.
2022-04-03 16:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
[7+ messages in thread]
回复: BUG #17454: Using psql without ipv4 address,the inet_server_port do not return PORT.
2022-04-03 01:37 UTC Wong Simon <thbytwo@live.cn>
Reconnect a single connection used by multiple threads in embedded SQL in C application causes error.
2022-02-21 12:09 UTC egashira.yusuke@fujitsu.com <egashira.yusuke@fujitsu.com>
` Re: Reconnect a single connection used by multiple threads in embedded SQL in C application causes error.
2022-02-21 21:29 UTC Noah Misch <noah@leadboat.com>
` RE: Reconnect a single connection used by multiple threads in embedded SQL in C application causes error.
2022-02-22 12:06 UTC egashira.yusuke@fujitsu.com <egashira.yusuke@fujitsu.com>
` Re: Reconnect a single connection used by multiple threads in embedded SQL in C application causes error.
2022-02-23 05:00 UTC Noah Misch <noah@leadboat.com>
` RE: Reconnect a single connection used by multiple threads in embedded SQL in C application causes error.
2022-02-25 11:29 UTC egashira.yusuke@fujitsu.com <egashira.yusuke@fujitsu.com>
` RE: Reconnect a single connection used by multiple threads in embedded SQL in C application causes error.
2022-03-02 12:43 UTC egashira.yusuke@fujitsu.com <egashira.yusuke@fujitsu.com>
` Re: Reconnect a single connection used by multiple threads in embedded SQL in C application causes error.
2022-03-03 01:12 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` RE: Reconnect a single connection used by multiple threads in embedded SQL in C application causes error.
2022-03-04 11:49 UTC egashira.yusuke@fujitsu.com <egashira.yusuke@fujitsu.com>
` Re: Reconnect a single connection used by multiple threads in embedded SQL in C application causes error.
2022-03-14 07:08 UTC Noah Misch <noah@leadboat.com>
` RE: Reconnect a single connection used by multiple threads in embedded SQL in C application causes error.
2022-03-25 13:34 UTC egashira.yusuke@fujitsu.com <egashira.yusuke@fujitsu.com>
` Re: Reconnect a single connection used by multiple threads in embedded SQL in C application causes error.
2022-04-02 07:27 UTC Noah Misch <noah@leadboat.com>
[11+ messages in thread]
BUG #17438: Logical replication hangs on master after huge DB load
2022-03-14 17:30 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17438: Logical replication hangs on master after huge DB load
2022-03-16 11:45 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #17438: Logical replication hangs on master after huge DB load
2022-03-16 12:09 UTC Sergey Belyashov <sergey.belyashov@gmail.com>
` Re: BUG #17438: Logical replication hangs on master after huge DB load
2022-03-29 12:03 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: BUG #17438: Logical replication hangs on master after huge DB load
2022-03-31 12:53 UTC Sergey Belyashov <sergey.belyashov@gmail.com>
` Re: BUG #17438: Logical replication hangs on master after huge DB load
2022-04-01 04:39 UTC Amit Kapila <amit.kapila16@gmail.com>
[6+ messages in thread]
Postgres Bug - Aggregate with order by
2022-03-31 20:04 UTC Andrew D <andrew.do1613@gmail.com>
` Re: Postgres Bug - Aggregate with order by
2022-03-31 20:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17452: IN caluse behaves differently when there is one item comapred to when multiple
2022-03-31 13:42 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17452: IN caluse behaves differently when there is one item comapred to when multiple
2022-03-31 16:06 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #17393: Delete database after recovery with point-in-time is still missing datafiles
2022-02-03 13:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17393: Delete database after recovery with point-in-time is still missing datafiles
2022-03-06 07:41 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #17393: Delete database after recovery with point-in-time is still missing datafiles
2022-03-30 19:07 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
` Re: BUG #17393: Delete database after recovery with point-in-time is still missing datafiles
2022-03-31 08:26 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #17393: Delete database after recovery with point-in-time is still missing datafiles
2022-03-31 16:04 UTC Pierre Forstmann <pierre.forstmann@gmail.com>
[5+ messages in thread]
Logical replication stops dropping used initial-sync replication slots
2022-03-17 14:24 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Logical replication stops dropping used initial-sync replication slots
2022-03-18 12:27 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Logical replication stops dropping used initial-sync replication slots
2022-03-21 14:18 UTC vignesh C <vignesh21@gmail.com>
` Re: Logical replication stops dropping used initial-sync replication slots
2022-03-21 14:43 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Logical replication stops dropping used initial-sync replication slots
2022-03-22 03:07 UTC vignesh C <vignesh21@gmail.com>
` Re: Logical replication stops dropping used initial-sync replication slots
2022-03-22 03:48 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Logical replication stops dropping used initial-sync replication slots
2022-03-22 07:02 UTC vignesh C <vignesh21@gmail.com>
` Re: Logical replication stops dropping used initial-sync replication slots
2022-03-22 11:26 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Logical replication stops dropping used initial-sync replication slots
2022-03-25 08:38 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Logical replication stops dropping used initial-sync replication slots
2022-03-29 11:27 UTC Amit Kapila <amit.kapila16@gmail.com>
` Re: Logical replication stops dropping used initial-sync replication slots
2022-03-29 12:01 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Logical replication stops dropping used initial-sync replication slots
2022-03-29 12:07 UTC Amit Kapila <amit.kapila16@gmail.com>
[12+ messages in thread]
BUG #17450: SUBSTRING function extracting lesser characters than specified
2022-03-28 10:30 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17450: SUBSTRING function extracting lesser characters than specified
2022-03-28 11:01 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: BUG #17450: SUBSTRING function extracting lesser characters than specified
2022-03-28 12:35 UTC Pavel Borisov <pashkin.elfe@gmail.com>
` Re: BUG #17450: SUBSTRING function extracting lesser characters than specified
2022-03-28 13:55 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17450: SUBSTRING function extracting lesser characters than specified
2022-03-28 14:00 UTC Japin Li <japinli@hotmail.com>
` Re: BUG #17450: SUBSTRING function extracting lesser characters than specified
2022-03-28 14:00 UTC Pavel Borisov <pashkin.elfe@gmail.com>
` Re: BUG #17450: SUBSTRING function extracting lesser characters than specified
2022-03-28 14:09 UTC David G. Johnston <david.g.johnston@gmail.com>
[7+ messages in thread]
(no subject)
2011-02-14 04:32 UTC Edwin Giraldo <eagiraldo91@yahoo.com>
` Re:
2011-02-14 07:25 UTC Jaime Casanova <jaime@2ndquadrant.com>
` BUG #17447: uninstaller fails
2022-03-24 19:09 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17447: uninstaller fails
2022-03-28 07:20 UTC Semab Tariq <semab.tariq@enterprisedb.com>
[4+ messages in thread]
OpenSSL v1.1.1n in postgres
2022-03-26 17:32 UTC Vibhu Chauhan (iDEAS-ER&D) <vibhu.chauhan@wipro.com>
` Re: OpenSSL v1.1.1n in postgres
2022-03-26 20:32 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: OpenSSL v1.1.1n in postgres
2022-03-26 20:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: OpenSSL v1.1.1n in postgres
2022-03-26 20:45 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: OpenSSL v1.1.1n in postgres
2022-03-26 21:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: OpenSSL v1.1.1n in postgres
2022-03-27 02:11 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
[6+ messages in thread]
BUG #17440: not expected result from jsonb_path_query
2022-03-15 16:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17440: not expected result from jsonb_path_query
2022-03-24 22:40 UTC Alexander Korotkov <aekorotkov@gmail.com>
[2+ messages in thread]
Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join
2022-03-21 11:45 UTC Prajna Shetty <Prajna.Shetty@mindtree.com>
` Re: Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join
2022-03-21 13:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join
2022-03-22 12:57 UTC Prajna Shetty <Prajna.Shetty@mindtree.com>
` Re: Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join
2022-03-24 11:55 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join
2022-03-24 12:24 UTC Justin Pryzby <pryzby@telsasoft.com>
[5+ messages in thread]
BUG #17444: ERROR: found xmin 215633 from before relfrozenxid 1280585
2022-03-21 13:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17444: ERROR: found xmin 215633 from before relfrozenxid 1280585
2022-03-24 09:05 UTC Andrey Borodin <x4mmm@yandex-team.ru>
[2+ messages in thread]
BUG #17446: Suggest updating the section title "Building Indexes Concurrently"
2022-03-22 21:58 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17446: Suggest updating the section title "Building Indexes Concurrently"
2022-03-23 04:39 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #17446: Suggest updating the section title "Building Indexes Concurrently"
2022-03-23 05:05 UTC David G. Johnston <david.g.johnston@gmail.com>
[3+ messages in thread]
BUG #17441: shm_mq receive less data than the sender sends
2022-03-20 08:39 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17441: shm_mq receive less data than the sender sends
2022-03-23 02:59 UTC Masahiko Sawada <sawada.mshk@gmail.com>
` Re: BUG #17441: shm_mq receive less data than the sender sends
2022-03-23 04:41 UTC Michael Paquier <michael@paquier.xyz>
[3+ messages in thread]
BUG #17445: "ON CONFLICT" has different behaviors when its param is passed with prepared stmt or hard coded
2022-03-21 20:37 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17445: "ON CONFLICT" has different behaviors when its param is passed with prepared stmt or hard coded
2022-03-21 22:23 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17445: "ON CONFLICT" has different behaviors when its param is passed with prepared stmt or hard coded
2022-03-21 22:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17445: "ON CONFLICT" has different behaviors when its param is passed with prepared stmt or hard coded
2022-03-21 22:50 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17445: "ON CONFLICT" has different behaviors when its param is passed with prepared stmt or hard coded
2022-03-21 22:53 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17445: "ON CONFLICT" has different behaviors when its param is passed with prepared stmt or hard coded
2022-03-21 23:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17445: "ON CONFLICT" has different behaviors when its param is passed with prepared stmt or hard coded
2022-03-21 23:14 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17445: "ON CONFLICT" has different behaviors when its param is passed with prepared stmt or hard coded
2022-03-21 23:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17445: "ON CONFLICT" has different behaviors when its param is passed with prepared stmt or hard coded
2022-03-21 23:49 UTC Peter Geoghegan <pg@bowt.ie>
[9+ 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