Peter Eisentraut e7128e8dbb Create function prototype as part of PG_FUNCTION_INFO_V1 macro ... Because of gcc -Wmissing-prototypes, all functions in dynamically loadable modules must have a separate prototype declaration. This is meant to detect global functions that are not declared in header files, but in cases where the function is called via dfmgr, this is redundant. Besides filling up space with boilerplate, this is a frequent source of compiler warnings in extension modules. We can fix that by creating the function prototype as part of the PG_FUNCTION_INFO_V1 macro, which such modules have to use anyway. That makes the code of modules cleaner, because there is one less place where the entry points have to be listed, and creates an additional check that functions have the right prototype. Remove now redundant prototypes from contrib and other modules.		2014-04-18 00:03:19 -04:00
..
Makefile	Allow background workers to be started dynamically.	2013-07-16 13:02:15 -04:00
worker_spi--1.0.sql	Allow discovery of whether a dynamic background worker is running.	2013-08-28 14:08:13 -04:00
worker_spi.c	Create function prototype as part of PG_FUNCTION_INFO_V1 macro	2014-04-18 00:03:19 -04:00
worker_spi.control	Allow background workers to be started dynamically.	2013-07-16 13:02:15 -04:00