pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17876: Function width_bucket() for float8 input returns value out of range
2023-03-29 08:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17876: Function width_bucket() for float8 input returns value out of range
2023-03-29 08:18 UTC Mats Kindahl <mats@timescale.com>
` Re: BUG #17876: Function width_bucket() for float8 input returns value out of range
2023-03-29 12:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17876: Function width_bucket() for float8 input returns value out of range
2023-03-30 07:54 UTC Mats Kindahl <mats@timescale.com>
` Re: BUG #17876: Function width_bucket() for float8 input returns value out of range
2023-03-30 15:35 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17876: Function width_bucket() for float8 input returns value out of range
2023-03-31 09:30 UTC Mats Kindahl <mats@timescale.com>
` Re: BUG #17876: Function width_bucket() for float8 input returns value out of range
2023-03-31 13:14 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17876: Function width_bucket() for float8 input returns value out of range
2023-04-05 07:58 UTC Mats Kindahl <mats@timescale.com>
` Re: BUG #17876: Function width_bucket() for float8 input returns value out of range
2023-04-05 21:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
[9+ messages in thread]
BUG #17887: EDB Community Installer for windows, locale selection not working properly
2023-04-05 17:32 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17886: Error disabling user triggers on a partitioned table
2023-04-04 16:47 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17886: Error disabling user triggers on a partitioned table
2023-04-04 16:49 UTC jazzl 0013 <jazz001319@gmail.com>
` Re: BUG #17886: Error disabling user triggers on a partitioned table
2023-04-04 18:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17886: Error disabling user triggers on a partitioned table
2023-04-05 07:33 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17886: Error disabling user triggers on a partitioned table
2023-04-05 16:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #17885: slow planning constraint_exclusion
2023-04-04 16:38 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17885: slow planning constraint_exclusion
2023-04-04 22:16 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17885: slow planning constraint_exclusion
2023-04-04 22:53 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17885: slow planning constraint_exclusion
2023-04-05 00:30 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #17885: slow planning constraint_exclusion
2023-04-05 00:45 UTC David Rowley <dgrowleyml@gmail.com>
[5+ messages in thread]
BUG #17883: Segmentation fault when create brin index on user-defined type.
2023-04-04 05:51 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17883: Segmentation fault when create brin index on user-defined type.
2023-04-04 12:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17882: I can't disable triggers on a table that has been partitioned
2023-04-02 15:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17882: I can't disable triggers on a table that has been partitioned
2023-04-02 16:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17881: Dependency error in Barman 3.5
2023-03-31 10:11 UTC PG Bug reporting form <noreply@postgresql.org>
` BUG #17881: Dependency error in Barman 3.5
2023-03-31 13:40 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17881: Dependency error in Barman 3.5 **SOLVED**
2023-03-31 22:09 UTC José María Terry Jiménez <jtj@tssystems.net>
` Re: BUG #17881: Dependency error in Barman 3.5
2023-03-31 22:17 UTC José María Terry Jiménez <jtj@tssystems.net>
[4+ messages in thread]
BUG #17880: Uninitialised value used when analyzing a table with an inheritance tree containing no children
2023-03-31 10:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17880: Uninitialised value used when analyzing a table with an inheritance tree containing no children
2023-03-31 13:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-27 08:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-27 14:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-27 21:28 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-27 21:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-28 02:27 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-28 03:05 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-28 03:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-28 04:54 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-28 06:13 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-28 06:21 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-28 06:28 UTC Maxim Boguk <maxim.boguk@gmail.com>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-28 18:24 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-28 18:31 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-28 18:33 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-28 18:38 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-28 22:03 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-30 19:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17871: JIT during postgresql_fdw remote_estimates EXPLAIN have very negatively effect on planning time
2023-03-31 12:40 UTC Maxim Boguk <maxim.boguk@gmail.com>
[18+ messages in thread]
BUG #17879: ERROR: unrecognized node type: 2139062143
2023-03-30 02:36 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17879: ERROR: unrecognized node type: 2139062143
2023-03-30 10:54 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17879: ERROR: unrecognized node type: 2139062143
2023-03-30 23:19 UTC David Rowley <dgrowleyml@gmail.com>
[3+ messages in thread]
BUG #17877: Referencing a system column in a foreign key leads to incorrect memory access
2023-03-29 14:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17877: Referencing a system column in a foreign key leads to incorrect memory access
2023-03-29 16:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17877: Referencing a system column in a foreign key leads to incorrect memory access
2023-03-30 09:57 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17877: Referencing a system column in a foreign key leads to incorrect memory access
2023-03-30 17:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2020-03-29 21:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2020-03-30 05:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2020-04-06 06:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2020-05-02 04:45 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2020-05-05 18:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2020-05-11 20:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2020-05-12 05:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2020-10-12 12:30 UTC Pavel Borisov <pashkin.elfe@gmail.com>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2020-10-12 16:03 UTC Pavel Borisov <pashkin.elfe@gmail.com>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2020-10-12 20:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2020-10-12 22:16 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2020-10-22 05:50 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2020-10-22 14:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2020-10-24 16:40 UTC Andrey Borodin <x4mmm@yandex-team.ru>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2020-11-02 16:55 UTC Pavel Borisov <pashkin.elfe@gmail.com>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2023-03-29 15:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2023-03-29 22:21 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2023-03-30 04:42 UTC Noah Misch <noah@leadboat.com>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2023-03-30 05:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering
2023-03-30 11:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
[20+ messages in thread]
Postgres common repo is missing geos310-3.10.3-1.rhel8.x86_64
2023-03-20 09:10 UTC Uytterhoeven Patrik <patrik.uytterhoeven@vlaanderen.be>
` Postgres common repo is missing geos310-3.10.3-1.rhel8.x86_64
2023-03-20 10:51 UTC Uytterhoeven Patrik <patrik.uytterhoeven@vlaanderen.be>
` Re: Postgres common repo is missing geos310-3.10.3-1.rhel8.x86_64
2023-03-23 12:29 UTC Devrim Gündüz <devrim@gunduz.org>
` Re: Postgres common repo is missing geos310-3.10.3-1.rhel8.x86_64
2023-03-30 08:45 UTC Devrim Gündüz <devrim@gunduz.org>
[4+ messages in thread]
Failed Upgrade during 11 to 15
2023-03-30 06:23 UTC prasad kumbhar <prasadrkumbhar@gmail.com>
` Re: Failed Upgrade during 11 to 15
2023-03-30 06:29 UTC prasad kumbhar <prasadrkumbhar@gmail.com>
[2+ messages in thread]
A structure has changed but comment modifications maybe missed
2023-03-25 14:43 UTC 甄明洋 <zhenmingyang@yeah.net>
` Re: A structure has changed but comment modifications maybe missed
2023-03-27 02:05 UTC Richard Guo <guofenglinux@gmail.com>
` Re: A structure has changed but comment modifications maybe missed
2023-03-27 02:19 UTC Richard Guo <guofenglinux@gmail.com>
` Re: A structure has changed but comment modifications maybe missed
2023-03-30 01:55 UTC David Rowley <dgrowleyml@gmail.com>
` Re: A structure has changed but comment modifications maybe missed
2023-03-30 02:02 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: A structure has changed but comment modifications maybe missed
2023-03-30 03:00 UTC David Rowley <dgrowleyml@gmail.com>
` Re: A structure has changed but comment modifications maybe missed
2023-03-30 03:07 UTC Andres Freund <andres@anarazel.de>
` Re: A structure has changed but comment modifications maybe missed
2023-03-30 03:33 UTC Richard Guo <guofenglinux@gmail.com>
` Re: A structure has changed but comment modifications maybe missed
2023-03-30 03:37 UTC David Rowley <dgrowleyml@gmail.com>
[9+ messages in thread]
Fwd: NEED RPM FILE OF LATEST POSTGRE supported for AIX 7.2
2023-03-28 10:57 UTC Amit Regmi <amitregmi111@gmail.com>
` Re: NEED RPM FILE OF LATEST POSTGRE supported for AIX 7.2
2023-03-28 20:49 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: NEED RPM FILE OF LATEST POSTGRE supported for AIX 7.2
2023-03-28 20:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: NEED RPM FILE OF LATEST POSTGRE supported for AIX 7.2
2023-03-29 04:24 UTC Amit Regmi <amitregmi111@gmail.com>
` Re: NEED RPM FILE OF LATEST POSTGRE supported for AIX 7.2
2023-03-29 05:32 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: NEED RPM FILE OF LATEST POSTGRE supported for AIX 7.2
2023-03-29 07:16 UTC Amit Regmi <amitregmi111@gmail.com>
` Re: NEED RPM FILE OF LATEST POSTGRE supported for AIX 7.2
2023-03-29 21:10 UTC Thomas Munro <thomas.munro@gmail.com>
[7+ messages in thread]
.wal file gets modified after .ready file is created
2023-03-29 19:42 UTC Kumar, Sachin <ssetiya@amazon.com>
CTE subquery referencing phantom records
2023-03-28 17:14 UTC Dave Bothwell <dbothwell@primepoint.com>
` Re: CTE subquery referencing phantom records
2023-03-28 19:31 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: CTE subquery referencing phantom records
2023-03-29 16:55 UTC Dave Bothwell <dbothwell@primepoint.com>
[3+ messages in thread]
BUG #17878: Stack Builder checksum failed
2023-03-29 16:19 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17874: Incorrect memory access at gistBuildCallback
2023-03-28 16:01 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17874: Incorrect memory access at gistBuildCallback
2023-03-29 10:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17874: Incorrect memory access at gistBuildCallback
2023-03-29 10:11 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17874: Incorrect memory access at gistBuildCallback
2023-03-29 11:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17874: Incorrect memory access at gistBuildCallback
2023-03-29 15:40 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
Problem install Stack builder download server
2023-03-29 08:44 UTC Balaguer, Jordi <jbalaguer@ghinduction.com>
BUG #17875: Postgres common repo is missing gdal32-libs-3.2.3-6.rhel8.x86_64/proj80-8.0.1-1.rhel8.x86_64
2023-03-28 20:26 UTC PG Bug reporting form <noreply@postgresql.org>
BUG #17872: Dropping an attribute of a composite type breaks indexes over the type silently
2023-03-27 10:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17872: Dropping an attribute of a composite type breaks indexes over the type silently
2023-03-27 14:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17872: Dropping an attribute of a composite type breaks indexes over the type silently
2023-03-27 16:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17872: Dropping an attribute of a composite type breaks indexes over the type silently
2023-03-27 18:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17872: Dropping an attribute of a composite type breaks indexes over the type silently
2023-03-27 18:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17872: Dropping an attribute of a composite type breaks indexes over the type silently
2023-03-27 19:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17872: Dropping an attribute of a composite type breaks indexes over the type silently
2023-03-27 19:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17872: Dropping an attribute of a composite type breaks indexes over the type silently
2023-03-28 16:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17872: Dropping an attribute of a composite type breaks indexes over the type silently
2023-03-28 19:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
[9+ messages in thread]
BUG #17775: Clarify default value for HEADER argument in documentation
2023-02-06 10:54 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17775: Clarify default value for HEADER argument in documentation
2023-03-28 18:12 UTC Bruce Momjian <bruce@momjian.us>
[2+ messages in thread]
(no subject)
2014-04-05 13:17 UTC Kanitchet Vaiassava <kanichet@hotmail.com>
` Re:
2014-04-05 15:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
` BUG #17870: Analyze on remote postgresql_fdw table never finish
2023-03-27 07:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17870: Analyze on remote postgresql_fdw table never finish
2023-03-27 14:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17870: Analyze on remote postgresql_fdw table never finish
2023-03-28 06:34 UTC Maxim Boguk <maxim.boguk@gmail.com>
[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