summaryrefslogtreecommitdiff
path: root/src/include/pg_config.h.in
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2010-02-13 02:34:16 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2010-02-13 02:34:16 +0000
commite08ab7c3127c10d419e91072c68e1bfeaab025b8 (patch)
tree8e46dc2510ed865e15b6a56fbf93bdbb10deb07e /src/include/pg_config.h.in
parentb95a720a487b5027af1b9e4a12542800598ff5de (diff)
downloadpostgresql-e08ab7c3127c10d419e91072c68e1bfeaab025b8.tar.gz
Support inlining various small performance-critical functions on non-GCC
compilers, by applying a configure check to see if the compiler will accept an unreferenced "static inline foo ..." function without warnings. It is believed that such warnings are the only reason not to declare inlined functions in headers, if the compiler understands "inline" at all. Kurt Harriman
Diffstat (limited to 'src/include/pg_config.h.in')
-rw-r--r--src/include/pg_config.h.in4
1 files changed, 4 insertions, 0 deletions
diff --git a/src/include/pg_config.h.in b/src/include/pg_config.h.in
index 69799a5042..684aed4a9f 100644
--- a/src/include/pg_config.h.in
+++ b/src/include/pg_config.h.in
@@ -749,6 +749,10 @@
(--enable-float8-byval) */
#undef USE_FLOAT8_BYVAL
+/* Define to 1 if "static inline" works without unwanted warnings from
+ compilations where static inline functions are defined but not called. */
+#undef USE_INLINE
+
/* Define to 1 if you want 64-bit integer timestamp and interval support.
(--enable-integer-datetimes) */
#undef USE_INTEGER_DATETIMES