13 Commits (f0ee42d59b797603d645df8876ae3abf6d016f1e)

Author	SHA1	Message	Date
Peter Eisentraut	66c04c981d	Mark some more variables as static or include the appropriate header ... Detected by clang's -Wmissing-variable-declarations. From: Andres Freund <andres@anarazel.de>	12 years ago
Bruce Momjian	7e04792a1c	Update copyright for 2014 ... Update all files in head, and files COPYRIGHT and legal.sgml in all back branches.	12 years ago
Peter Eisentraut	001e114b8d	Fix whitespace issues found by git diff --check, add gitattributes ... Set per file type attributes in .gitattributes to fine-tune whitespace checks. With the associated cleanups, the tree is now clean for git	12 years ago
Tom Lane	5f1ab46101	Suppress a couple of compiler warnings seen with older gcc versions. ... To wit, bgworker.c: In function `RegisterDynamicBackgroundWorker': bgworker.c:761: warning: `generation' might be used uninitialized in this function dsm_impl.c: In function `dsm_impl_op': dsm_impl.c:197: warning: control reaches end of non-void function Neither of these represent actual bugs, but we may as well tweak the code so that more compilers can tell that. This won't change the generated code on compilers that do recognize that the cases are unreachable.	12 years ago
Robert Haas	523beaa11b	Provide a reliable mechanism for terminating a background worker. ... Although previously-introduced APIs allow the process that registers a background worker to obtain the worker's PID, there's no way to prevent a worker that is not currently running from being restarted. This patch introduces a new API TerminateBackgroundWorker() that prevents the background worker from being restarted, terminates it if it is currently running, and causes it to be unregistered if or when it is not running. Patch by me. Review by Michael Paquier and KaiGai Kohei.	12 years ago
Robert Haas	496439d943	Fix compiler warning in WaitForBackgroundWorkerStartup(). ... Per complaint from Andrew Gierth.	12 years ago
Robert Haas	090d0f2050	Allow discovery of whether a dynamic background worker is running. ... Using the infrastructure provided by this patch, it's possible either to wait for the startup of a dynamically-registered background worker, or to poll the status of such a worker without waiting. In either case, the current PID of the worker process can also be obtained. As usual, worker_spi is updated to demonstrate the new functionality. Patch by me. Review by Andres Freund.	13 years ago
Robert Haas	2dee7998f9	Move more bgworker code to bgworker.c; also, some renaming. ... Per discussion on pgsql-hackers. Michael Paquier, slightly modified by me. Original suggestion from Amit Kapila.	13 years ago
Peter Eisentraut	9d775d8894	Message style improvements	13 years ago
Robert Haas	149e38e5ee	Assorted bgworker-related comment fixes. ... Per gripes by Amit Kapila.	13 years ago
Tom Lane	fa2fad3c06	Improve ilist.h's support for deletion of slist elements during iteration. ... Previously one had to use slist_delete(), implying an additional scan of the list, making this infrastructure considerably less efficient than traditional Lists when deletion of element(s) in a long list is needed. Modify the slist_foreach_modify() macro to support deleting the current element in O(1) time, by keeping a "prev" pointer in addition to "cur" and "next". Although this makes iteration with this macro a bit slower, no real harm is done, since in any scenario where you're not going to delete the current list element you might as well just use slist_foreach instead. Improve the comments about when to use each macro. Back-patch to 9.3 so that we'll have consistent semantics in all branches that provide ilist.h. Note this is an ABI break for callers of slist_foreach_modify(). Andres Freund and Tom Lane	13 years ago
Robert Haas	f40a318eea	Remove bgw_sighup and bgw_sigterm. ... Per discussion on pgsql-hackers, these aren't really needed. Interim versions of the background worker patch had the worker starting with signals already unblocked, which would have made this necessary. But the final version does not, so we don't really need it; and it doesn't work well with the new facility for starting dynamic background workers, so just rip it out. Also per discussion on pgsql-hackers, back-patch this change to 9.3. It's best to get the API break out of the way before we do an official release of this facility, to avoid more pain for extension authors later.	13 years ago
Robert Haas	7f7485a0cd	Allow background workers to be started dynamically. ... There is a new API, RegisterDynamicBackgroundWorker, which allows an ordinary user backend to register a new background writer during normal running. This means that it's no longer necessary for all background workers to be registered during processing of shared_preload_libraries, although the option of registering workers at that time remains available. When a background worker exits and will not be restarted, the slot previously used by that background worker is automatically released and becomes available for reuse. Slots used by background workers that are configured for automatic restart can't (yet) be released without shutting down the system. This commit adds a new source file, bgworker.c, and moves some of the existing control logic for background workers there. Previously, there was little enough logic that it made sense to keep everything in postmaster.c, but not any more. This commit also makes the worker_spi contrib module into an extension and adds a new function, worker_spi_launch, which can be used to demonstrate the new facility.	13 years ago