postgresql/contrib/Makefile

87 lines
1.2 KiB
Makefile
Raw Normal View History

2010-09-21 04:08:53 +08:00
# contrib/Makefile
2000-06-16 02:55:34 +08:00
subdir = contrib
top_builddir = ..
include $(top_builddir)/src/Makefile.global
2000-06-16 02:55:34 +08:00
SUBDIRS = \
adminpack \
auth_delay \
auto_explain \
btree_gin \
btree_gist \
2001-08-24 00:54:25 +08:00
chkpass \
citext \
2000-12-12 04:40:59 +08:00
cube \
2001-06-19 01:20:56 +08:00
dblink \
dict_int \
dict_xsyn \
dummy_seclabel \
earthdistance \
file_fdw \
fuzzystrmatch \
hstore \
2002-08-30 09:44:00 +08:00
intagg \
intarray \
isn \
2001-02-10 20:07:12 +08:00
lo \
ltree \
oid2name \
pageinspect \
passwordcheck \
pg_archivecleanup \
pg_buffercache \
pg_freespacemap \
pg_standby \
pg_stat_statements \
pg_test_fsync \
pg_test_timing \
pg_trgm \
pg_upgrade \
pg_upgrade_support \
2000-06-16 02:55:34 +08:00
pgbench \
pgcrypto \
2006-04-23 10:17:59 +08:00
pgrowlocks \
2001-10-01 09:52:38 +08:00
pgstattuple \
postgres_fdw \
2001-02-10 20:07:12 +08:00
seg \
spi \
2002-07-31 00:32:20 +08:00
tablefunc \
tcn \
test_parser \
tsearch2 \
2009-08-18 18:34:39 +08:00
unaccent \
Background worker processes Background workers are postmaster subprocesses that run arbitrary user-specified code. They can request shared memory access as well as backend database connections; or they can just use plain libpq frontend database connections. Modules listed in shared_preload_libraries can register background workers in their _PG_init() function; this is early enough that it's not necessary to provide an extra GUC option, because the necessary extra resources can be allocated early on. Modules can install more than one bgworker, if necessary. Care is taken that these extra processes do not interfere with other postmaster tasks: only one such process is started on each ServerLoop iteration. This means a large number of them could be waiting to be started up and postmaster is still able to quickly service external connection requests. Also, shutdown sequence should not be impacted by a worker process that's reasonably well behaved (i.e. promptly responds to termination signals.) The current implementation lets worker processes specify their start time, i.e. at what point in the server startup process they are to be started: right after postmaster start (in which case they mustn't ask for shared memory access), when consistent state has been reached (useful during recovery in a HOT standby server), or when recovery has terminated (i.e. when normal backends are allowed). In case of a bgworker crash, actions to take depend on registration data: if shared memory was requested, then all other connections are taken down (as well as other bgworkers), just like it were a regular backend crashing. The bgworker itself is restarted, too, within a configurable timeframe (which can be configured to be never). More features to add to this framework can be imagined without much effort, and have been discussed, but this seems good enough as a useful unit already. An elementary sample module is supplied. Author: Álvaro Herrera This patch is loosely based on prior patches submitted by KaiGai Kohei, and unsubmitted code by Simon Riggs. Reviewed by: KaiGai Kohei, Markus Wanner, Andres Freund, Heikki Linnakangas, Simon Riggs, Amit Kapila
2012-12-07 01:57:52 +08:00
vacuumlo \
worker_spi
ifeq ($(with_openssl),yes)
SUBDIRS += sslinfo
else
ALWAYS_SUBDIRS += sslinfo
endif
ifeq ($(with_ossp_uuid),yes)
SUBDIRS += uuid-ossp
else
ALWAYS_SUBDIRS += uuid-ossp
endif
2007-04-15 20:48:24 +08:00
ifeq ($(with_libxml),yes)
SUBDIRS += xml2
else
ALWAYS_SUBDIRS += xml2
2007-04-15 20:48:24 +08:00
endif
ifeq ($(with_selinux),yes)
SUBDIRS += sepgsql
else
ALWAYS_SUBDIRS += sepgsql
endif
# Missing:
# start-scripts \ (does not have a makefile)
2007-04-15 20:48:24 +08:00
$(recurse)
$(recurse_always)