pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18449: Altering column type fails when an SQL routine depends on the column
2024-04-27 04:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18449: Altering column type fails when an SQL routine depends on the column
2024-04-28 01:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18449: Altering column type fails when an SQL routine depends on the column
2024-05-01 13:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18449: Altering column type fails when an SQL routine depends on the column
2024-05-01 14:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18449: Altering column type fails when an SQL routine depends on the column
2024-05-02 04:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18449: Altering column type fails when an SQL routine depends on the column
2024-05-02 21:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18449: Altering column type fails when an SQL routine depends on the column
2024-05-03 07:01 UTC Peter Eisentraut <peter@eisentraut.org>
[7+ messages in thread]
BUG #18455: DST information is flagged wrongly
2024-05-02 12:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18455: DST information is flagged wrongly
2024-05-02 15:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18455: DST information is flagged wrongly
2024-05-02 16:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18455: DST information is flagged wrongly
2024-05-02 16:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #18454: Reproducible SIGSEGV in query
2024-05-02 11:57 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18451: NULL fails to coerce to string when performing string comparison
2024-04-30 01:16 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18451: NULL fails to coerce to string when performing string comparison
2024-04-30 21:13 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18451: NULL fails to coerce to string when performing string comparison
2024-04-30 21:25 UTC Darryl Dixon <darryl.dixon@gmail.com>
` Re: BUG #18451: NULL fails to coerce to string when performing string comparison
2024-04-30 21:34 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18451: NULL fails to coerce to string when performing string comparison
2024-04-30 21:38 UTC Darryl Dixon <darryl.dixon@gmail.com>
` Re: BUG #18451: NULL fails to coerce to string when performing string comparison
2024-04-30 22:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18451: NULL fails to coerce to string when performing string comparison
2024-04-30 22:08 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18451: NULL fails to coerce to string when performing string comparison
2024-04-30 22:09 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18451: NULL fails to coerce to string when performing string comparison
2024-04-30 22:11 UTC Darryl Dixon <darryl.dixon@gmail.com>
` Re: BUG #18451: NULL fails to coerce to string when performing string comparison
2024-04-30 22:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18451: NULL fails to coerce to string when performing string comparison
2024-05-01 02:34 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18451: NULL fails to coerce to string when performing string comparison
2024-05-01 02:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18451: NULL fails to coerce to string when performing string comparison
2024-05-01 15:25 UTC David G. Johnston <david.g.johnston@gmail.com>
[13+ messages in thread]
BUG #18453: --exclude-database has problems with capital letters
2024-04-30 23:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18453: --exclude-database has problems with capital letters
2024-05-01 00:09 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18453: --exclude-database has problems with capital letters
2024-05-01 00:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18453: --exclude-database has problems with capital letters
2024-05-01 11:12 UTC Jernej Simončič <jernej-s31+pg@simoncic.si>
[4+ messages in thread]
BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2023-03-20 14:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2023-03-22 06:18 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2023-03-23 03:10 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2023-03-23 03:25 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2023-03-23 04:01 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2023-03-23 04:27 UTC Peter Geoghegan <pg@bowt.ie>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2023-03-23 04:56 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2023-03-25 05:32 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2023-09-09 08:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2024-04-24 02:25 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2024-04-24 13:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2024-04-25 15:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2024-04-29 00:54 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2024-04-29 14:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2024-04-29 14:28 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2024-04-30 00:48 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2024-04-30 14:54 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2024-04-30 15:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17855: Uninitialised memory used when the name type value processed in binary mode of Memoize
2024-05-01 01:30 UTC David Rowley <dgrowleyml@gmail.com>
[19+ messages in thread]
BUG #18452: [PostgreSQL and 16.1]: [Postgres.exe crash observed while installing the application]
2024-04-30 21:12 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18452: [PostgreSQL and 16.1]: [Postgres.exe crash observed while installing the application]
2024-04-30 21:50 UTC Thomas Munro <thomas.munro@gmail.com>
[2+ messages in thread]
Unable to connect to server
2024-04-29 04:33 UTC Javali, Pramod <Pramod.Javali1@T-Mobile.com>
` Re: Unable to connect to server
2024-04-29 14:23 UTC Kashif Zeeshan <kashi.zeeshan@gmail.com>
` Re: Unable to connect to server
2024-04-29 15:26 UTC Jeff Janes <jeff.janes@gmail.com>
` RE: Unable to connect to server
2024-04-30 02:20 UTC Javali, Pramod <Pramod.Javali1@t-mobile.com>
[4+ messages in thread]
DETAIL: pg_rewind: servers diverged at WAL location 0/9000000 on timeline 1
2024-04-26 19:06 UTC Kumar, Devesh <devesh.kumar@cmegroup.com>
` Re: DETAIL: pg_rewind: servers diverged at WAL location 0/9000000 on timeline 1
2024-04-29 10:07 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: DETAIL: pg_rewind: servers diverged at WAL location 0/9000000 on timeline 1
2024-04-29 10:25 UTC Kumar, Devesh <devesh.kumar@cmegroup.com>
[3+ messages in thread]
回复：Re: BUG #18450: The memory usage of the postgresql12.6 walsender process is abnormally high.
2024-04-29 06:42 UTC Melody <melody_xiaodi@sina.com>
BUG #18450: The memory usage of the postgresql12.6 walsender process is abnormally high.
2024-04-27 06:02 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18450: The memory usage of the postgresql12.6 walsender process is abnormally high.
2024-04-27 21:45 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18445: date_part / extract range for hours do not match documentation
2024-04-23 10:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18445: date_part / extract range for hours do not match documentation
2024-04-23 14:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18445: date_part / extract range for hours do not match documentation
2024-04-26 10:23 UTC Marek Läll <lall.marek@gmail.com>
` Re: BUG #18445: date_part / extract range for hours do not match documentation
2024-04-26 13:06 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18445: date_part / extract range for hours do not match documentation
2024-04-26 19:27 UTC Marek Läll <lall.marek@gmail.com>
` Re: BUG #18445: date_part / extract range for hours do not match documentation
2024-04-26 19:36 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18445: date_part / extract range for hours do not match documentation
2024-04-26 20:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
[7+ messages in thread]
BUG #17690: Nonresponsive client on replica can halt replication indefinitely
2022-11-18 19:21 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17690: Nonresponsive client on replica can halt replication indefinitely
2024-04-25 22:18 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: BUG #17690: Nonresponsive client on replica can halt replication indefinitely
2024-04-25 23:58 UTC Jacob Baskin <jacob.baskin@gmail.com>
[3+ messages in thread]
BUG #15954: Unable to alter partitioned table to set logged
2019-08-13 18:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2019-08-14 01:47 UTC Amit Langote <amitlangote09@gmail.com>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2019-08-14 01:57 UTC David Rowley <david.rowley@2ndquadrant.com>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2019-08-14 02:48 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #15954: Unable to alter partitioned table to set log
2019-08-14 02:51 UTC Efrain J. Berdecia <ejberdecia@yahoo.com>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2019-08-14 03:17 UTC David Rowley <david.rowley@2ndquadrant.com>
` Re: BUG #15954: Unable to alter partitioned table to set log
2019-08-14 03:26 UTC David Rowley <david.rowley@2ndquadrant.com>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2019-08-14 03:32 UTC Efrain J. Berdecia <ejberdecia@yahoo.com>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2019-08-14 03:35 UTC Keith Fiske <keith.fiske@crunchydata.com>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2019-08-14 03:41 UTC Keith Fiske <keith.fiske@crunchydata.com>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2019-08-14 05:32 UTC David Rowley <david.rowley@2ndquadrant.com>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2019-08-14 12:46 UTC Efrain J. Berdecia <ejberdecia@yahoo.com>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2019-08-21 13:24 UTC Keith Fiske <keith.fiske@crunchydata.com>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2019-08-21 13:44 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2019-08-22 08:14 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2019-08-22 14:37 UTC Keith Fiske <keith.fiske@crunchydata.com>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2024-04-22 19:36 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2024-04-23 05:37 UTC Michael Paquier <michael@paquier.xyz>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2024-04-23 12:33 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #15954: Unable to alter partitioned table to set logged
2024-04-24 07:24 UTC Michael Paquier <michael@paquier.xyz>
[20+ messages in thread]
BUG #18446: Postgres.exe crash observed while installing the application
2024-04-23 20:41 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #18426: Canceling vacuum while truncating a relation leads to standby PANIC
2024-04-10 11:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18426: Canceling vacuum while truncating a relation leads to standby PANIC
2024-04-10 18:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18426: Canceling vacuum while truncating a relation leads to standby PANIC
2024-04-12 06:41 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18426: Canceling vacuum while truncating a relation leads to standby PANIC
2024-04-12 06:43 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18426: Canceling vacuum while truncating a relation leads to standby PANIC
2024-04-12 11:14 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: BUG #18426: Canceling vacuum while truncating a relation leads to standby PANIC
2024-04-23 20:26 UTC Thomas Munro <thomas.munro@gmail.com>
[6+ messages in thread]
回复： BUG #18437: The index scan result is more than the full scan result, and the primary key index has duplicate val
2024-04-23 15:44 UTC 1165125080 <1165125080@qq.com>
Error during installation on a 64 bit Windows 10 Korean environment using postgresql-15.6-1-windows-x64.exe
2024-04-23 15:02 UTC Carl <pginstallissueko@gmail.com>
BUG #18442: Unnecessary Sort operator in indexScan Plan
2024-04-19 03:10 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18442: Unnecessary Sort operator in indexScan Plan
2024-04-19 14:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18442: Unnecessary Sort operator in indexScan Plan
2024-04-22 01:53 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18442: Unnecessary Sort operator in indexScan Plan
2024-04-22 02:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18442: Unnecessary Sort operator in indexScan Plan
2024-04-22 06:16 UTC Richard Guo <guofenglinux@gmail.com>
` Re: BUG #18442: Unnecessary Sort operator in indexScan Plan
2024-04-22 22:56 UTC David Rowley <dgrowleyml@gmail.com>
[6+ messages in thread]
BUG #18443: jsonb_agg issue. Again.
2024-04-19 14:09 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18443: jsonb_agg issue. Again.
2024-04-19 15:34 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18443: jsonb_agg issue. Again.
2024-04-19 17:21 UTC Ц <pfunk@mail.ru>
` Re: BUG #18443: jsonb_agg issue. Again.
2024-04-19 17:31 UTC Ц <pfunk@mail.ru>
` Re: BUG #18443: jsonb_agg issue. Again.
2024-04-19 17:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #18351: VACUUM FULL fails with error: missing chunk number 0 for toast value XXX
2024-02-17 20:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18351: VACUUM FULL fails with error: missing chunk number 0 for toast value XXX
2024-02-27 09:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18351: VACUUM FULL fails with error: missing chunk number 0 for toast value XXX
2024-03-05 18:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #18351: VACUUM FULL fails with error: missing chunk number 0 for toast value XXX
2024-04-19 13:22 UTC Peter Petrov <p.petrov@postgrespro.ru>
[4+ messages in thread]
CVE-2024-28849
2024-04-18 15:27 UTC Mathews, Rob <rpmathe@sandia.gov>
` Re: CVE-2024-28849
2024-04-18 17:25 UTC Jonathan S. Katz <jkatz@postgresql.org>
` Re: CVE-2024-28849
2024-04-18 17:37 UTC Jerry Sievert <jerry@legitimatesounding.com>
[3+ messages in thread]
BUG #18428: Connection broken but DB service still alive.
2024-04-12 08:14 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18428: Connection broken but DB service still alive.
2024-04-12 13:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18428: Connection broken but DB service still alive.
2024-04-18 01:23 UTC 盧致均(Harry) <harry@linktech.com.tw>
[3+ messages in thread]
BUG #18411: Unable to create database with owner on AWS RDS
2024-03-27 17:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18411: Unable to create database with owner on AWS RDS
2024-03-27 21:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18411: Unable to create database with owner on AWS RDS
2024-03-28 01:25 UTC Andrey Lizenko <lizenko79@gmail.com>
` Re: BUG #18411: Unable to create database with owner on AWS RDS
2024-03-28 01:45 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18411: Unable to create database with owner on AWS RDS
2024-03-28 05:20 UTC Andrey Lizenko <lizenko79@gmail.com>
` Re: BUG #18411: Unable to create database with owner on AWS RDS
2024-03-28 05:31 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18411: Unable to create database with owner on AWS RDS
2024-04-17 14:42 UTC Myka Dresser <myanodress@gmail.com>
` BUG #18411: Unable to create database with owner on AWS RDS
2024-04-17 14:49 UTC David G. Johnston <david.g.johnston@gmail.com>
[8+ messages in thread]
BUG #18440: Query does not prune partitions correctly or use index when prepared statements are used
2024-04-16 14:08 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18440: Query does not prune partitions correctly or use index when prepared statements are used
2024-04-16 19:20 UTC David G. Johnston <david.g.johnston@gmail.com>
[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