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-06-18T15:21:51Z Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Tom Lane <tgl@sss.pgh.pa.us>
2025-06-18T13:46:38Z Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Phineas Jensen <phin@zayda.net>
2025-06-18T10:29:48Z Re: BUG #18959: Name collisions of expression indexes during parallel Index creations on a pratitioned table. Dilip Kumar <dilipbalaut@gmail.com>
2025-06-18T06:33:49Z Re: BUG #18947: TRAP: failed Assert("len_to_wrt >= 0") in pg_stat_statements Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
2025-06-17T20:10:07Z Re: BUG #18942: walsender memory allocation failure adding snapshot and invalidations to logical replica w/PG 16.9 Laurence Parry <greenreaper@hotmail.com>
2025-06-17T17:45:15Z Re: Logical replication 'ERROR: invalid memory alloc request size 1831213792' after upgrading to 15.13 Masahiko Sawada <sawada.mshk@gmail.com>
2025-06-17T17:42:41Z Re: [E] Re: BUG #18938: Logical replication failure in 16.9: "invalid memory alloc request size 1372786672" Masahiko Sawada <sawada.mshk@gmail.com>
2025-06-17T17:41:51Z Re: BUG #18942: walsender memory allocation failure adding snapshot and invalidations to logical replica w/PG 16.9 Masahiko Sawada <sawada.mshk@gmail.com>
2025-06-17T17:40:36Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 Masahiko Sawada <sawada.mshk@gmail.com>
2025-06-17T16:29:11Z Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Tom Lane <tgl@sss.pgh.pa.us>
2025-06-17T02:20:20Z Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Richard Guo <guofenglinux@gmail.com>
2025-06-16T15:24:55Z Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Tom Lane <tgl@sss.pgh.pa.us>
2025-06-16T07:22:49Z Re: BUG #18953: Planner fails to build plan for complex query with LATERAL references Richard Guo <guofenglinux@gmail.com>
2025-06-16T02:32:54Z Re: Invalid control file checksum with AVX-512 during initdb on a clang19 -O0 build John Naylor <johncnaylorls@gmail.com>
2025-06-16T02:27:50Z Re: Logical replication 'invalid memory alloc request size 1585837200' after upgrading to 17.5 vignesh C <vignesh21@gmail.com>
2025-06-15T21:41:37Z Re: Lower priority of the configure option --with-libraries causes wrong lib resolution Has attachments Tom Lane <tgl@sss.pgh.pa.us>
2025-06-15T20:26:01Z Re: Lower priority of the configure option --with-libraries causes wrong lib resolution Tom Lane <tgl@sss.pgh.pa.us>
2025-06-15T16:20:11Z Lower priority of the configure option --with-libraries causes wrong lib resolution Charles Samborski <demurgos@demurgos.net>
2025-06-15T01:23:41Z Re: Invalid control file checksum with AVX-512 during initdb on a clang19 -O0 build Andy Fan <zhihuifan1213@163.com>
2025-06-14T22:26:37Z Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Tom Lane <tgl@sss.pgh.pa.us>
2025-06-14T21:35:20Z Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Has attachments Lowell Hought <lowell.hought@gmail.com>
2025-06-14T16:12:17Z Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Tom Lane <tgl@sss.pgh.pa.us>
2025-06-14T15:52:38Z Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Lowell Hought <lowell.hought@gmail.com>
2025-06-14T15:15:48Z Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Tom Lane <tgl@sss.pgh.pa.us>
2025-06-14T14:27:19Z Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17 Lowell Hought <lowell.hought@gmail.com>