News for hackers. Stuff that matters.

A comment on Important PostgreSQL 14 update to avoid silent corruption of indexes. Parent comment

Re:Important PostgreSQL 14 update to avoid silent corruption... by plq on Thursday June 09, 2022 @10:42PM (#31689379)
While I'm not sure that was a consideration here, sometimes C compilers produce better machine code when they got access to more function definitions. Eg. Sqlite recommends that embedders use the single ~10mb sqlite.c file[1] for both ease of use and performance reasons.

[1]: https://www.sqlite.org/amalgamation.html

[ Parent | on HN ]
Re:Important PostgreSQL 14 update to avoid silent corruption... by colordrops on Thursday June 09, 2022 @11:11PM (#31689536)
Seems like something the compiler should take care of.
[ Parent | on HN ]
Re:Important PostgreSQL 14 update to avoid silent corruption... by fjfbsufhdvfy on Friday June 10, 2022 @12:43AM (#31690138)
It can when you use LTO, but that tends to be very slow for large programs.
[ Parent | on HN ]
Re:Important PostgreSQL 14 update to avoid silent corruption... by plq on Friday June 10, 2022 @06:57AM (#31692362)
It is slow. Our (C++) project's MSVC release build ends with a glorious 2-minute run of link.exe with lto (/LTCG /O2) and aggressive inlining (/Ob3) enabled.

Limiting unit size in C++ helps with faster edit/compile/run cycles as well, which doesn't seem to be concern for C codebases in 21st century.

[ Parent | on HN ]
Re:Important PostgreSQL 14 update to avoid silent corruption... by anarazel on Friday June 10, 2022 @05:56PM (#31699801)
You hit most of the same issues (and some additional ones) when compiling the same code within one translation unit...
[ Parent | on HN ]