Horton
Menu

Messages in pgsql-bugs

Same data as JSON: GET /api/v1/messages same messages as JSON; filter by `list`, `from`/`to`. API reference →
Date ▼ SubjectFrom
2025-07-03T12:30:40Z Re: BUG #18976: -0.0 with float8 will be transformed to 0 inprepare statement but not in normal execution ZhangChi <798604270@qq.com>
2025-07-03T12:23:42Z Re: BUG #18976: -0.0 with float8 will be transformed to 0 in prepare statement but not in normal execution Laurenz Albe <laurenz.albe@cybertec.at>
2025-07-03T03:03:05Z BUG #18976: -0.0 with float8 will be transformed to 0 in prepare statement but not in normal execution PG Bug reporting form <noreply@postgresql.org>
2025-07-02T19:21:50Z Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries Tom Lane <tgl@sss.pgh.pa.us>
2025-07-02T13:49:50Z Re: BUG #18975: PostgreSQL server doesn't process SQL request correctly over Windows replica of Linux server Laurenz Albe <laurenz.albe@cybertec.at>
2025-07-02T08:44:30Z Re: BUG #16931: source code problem about commit_ts Fujii Masao <masao.fujii@oss.nttdata.com>
2025-07-02T07:44:51Z Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries Sergei Kornilov <sk@zsrv.org>
2025-07-02T07:04:12Z Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries Maxim Boguk <maxim.boguk@gmail.com>
2025-07-02T06:35:21Z Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries Maxim Boguk <maxim.boguk@gmail.com>
2025-07-02T06:32:09Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada <sawada.mshk@gmail.com>
2025-07-02T01:42:32Z Re: BUG #16931: source code problem about commit_ts Has attachments Andy Fan <zhihuifan1213@163.com>
2025-07-02T00:45:52Z [PATCH v1 1/1] Remove xl_commit_ts_set. Andy Fan <zhihuifan1213@163.com>
2025-07-02T00:03:00Z Re: BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries Maxim Boguk <maxim.boguk@gmail.com>
2025-07-01T23:10:12Z BUG #18975: PostgreSQL server doesn't process SQL request correctly over Windows replica of Linux server PG Bug reporting form <noreply@postgresql.org>
2025-07-01T22:08:57Z BUG #18974: Postgresql repeatable crash after pg_upgrade from 15 to 17.5 version in postgresql_fdw queries PG Bug reporting form <noreply@postgresql.org>
2025-07-01T19:52:57Z Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure Tom Lane <tgl@sss.pgh.pa.us>
2025-07-01T19:41:32Z Re: BUG #18897: Logical replication conflict after using pg_createsubscriber under heavy load Has attachments Shlok Kyal <shlok.kyal.oss@gmail.com>
2025-07-01T06:49:09Z Re: BUG #18943: Return value of a function 'xmlBufferCreate' is dereferenced at xpath.c:177 without checking for NUL Michael Paquier <michael@paquier.xyz>
2025-07-01T03:25:20Z Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure Has attachments jian he <jian.universality@gmail.com>
2025-06-30T15:14:43Z Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure Tom Lane <tgl@sss.pgh.pa.us>
2025-06-30T14:56:58Z Re: BUG #18973: The default enable_material=ON affects the cost estimation of optimizer, resulting in 10968x slow Tom Lane <tgl@sss.pgh.pa.us>
2025-06-30T13:44:19Z BUG #18973: The default enable_material=ON affects the cost estimation of optimizer, resulting in 10968x slow PG Bug reporting form <noreply@postgresql.org>
2025-06-30T06:04:25Z Re: BUG #18970: Atempt to alter type of table column used in row type with check leads to assertion failure Has attachments jian he <jian.universality@gmail.com>
2025-06-30T03:40:37Z Re: Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13 Masahiko Sawada <sawada.mshk@gmail.com>
2025-06-30T03:28:33Z Re: BUG #18961: Race scenario where max_standby_streaming_delay is not honored Dilip Kumar <dilipbalaut@gmail.com>