postgresql - postgresql mirror

	Commit message (Collapse)	Author	Age
*	Fix typos in various places	Michael Paquier	2019-06-03
\| \| \| \| \| \|	Author: Andrea Gelmini Reviewed-by: Michael Paquier, Justin Pryzby Discussion: https://postgr.es/m/20190528181718.GA39034@glet
*	Fix collection of typos and grammar mistakes in docs and comments	Michael Paquier	2019-04-19
\| \| \| \| \|	Author: Justin Pryzby Discussion: https://postgr.es/m/20190330224333.GQ5815@telsasoft.com
*	llvm: Fix file-ending in IDENTIFICATION comments.	Andres Freund	2019-01-22
\| \| \| \| \| \|	Author: Amit Langote Discussion: https://postgr.es/m/9a54dcef-c799-ce89-2e47-0a7fc12d5fc2@lab.ntt.co.jp Backpatch: 11-, where llvm was introduced.
*	Update copyright for 2019	Bruce Momjian	2019-01-02
\| \| \| \|	Backpatch-through: certain files through 9.4
*	LLVMJIT: Check for 'noinline' attribute in recursively inlined functions.	Andres Freund	2018-07-25
\| \| \| \| \| \| \| \| \| \| \| \|	Previously the attribute was only checked for external functions inlined, not "static" functions that had to be inlined as dependencies. This isn't really a bug, but makes debugging a bit harder. The new behaviour also makes more sense. Therefore backpatch. Author: Andres Freund Backpatch: 11-, where JIT compilation was added
*	Add inlining support to LLVM JIT provider.	Andres Freund	2018-03-28
	This provides infrastructure to allow JITed code to inline code implemented in C. This e.g. can be postgres internal functions or extension code. This already speeds up long running queries, by allowing the LLVM optimizer to optimize across function boundaries. The optimization potential currently doesn't reach its full potential because LLVM cannot optimize the FunctionCallInfoData argument fully away, because it's allocated on the heap rather than the stack. Fixing that is beyond what's realistic for v11. To be able to do that, use CLANG to convert C code to LLVM bitcode, and have LLVM build a summary for it. That bitcode can then be used to to inline functions at runtime. For that the bitcode needs to be installed. Postgres bitcode goes into $pkglibdir/bitcode/postgres, extensions go into equivalent directories. PGXS has been modified so that happens automatically if postgres has been compiled with LLVM support. Currently this isn't the fastest inline implementation, modules are reloaded from disk during inlining. That's to work around an apparent LLVM bug, triggering an apparently spurious error in LLVM assertion enabled builds. Once that is resolved we can remove the superfluous read from disk. Docs will follow in a later commit containing docs for the whole JIT feature. Author: Andres Freund Discussion: https://postgr.es/m/20170901064131.tazjxwus3k2w3ybh@alap3.anarazel.de