mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-12-27 08:39:28 +08:00
d894941663
The user can whitelist specified extension(s) in the foreign server's options, whereupon we will treat immutable functions and operators of those extensions as candidates to be sent for remote execution. Whitelisting an extension in this way basically promises that the extension exists on the remote server and behaves compatibly with the local instance. We have no way to prove that formally, so we have to rely on the user to get it right. But this seems like something that people can usually get right in practice. We might in future allow functions and operators to be whitelisted individually, but extension granularity is a very convenient special case, so it got done first. The patch as-committed lacks any regression tests, which is unfortunate, but introducing dependencies on other extensions for testing purposes would break "make installcheck" scenarios, which is worse. I have some ideas about klugy ways around that, but it seems like material for a separate patch. For the moment, leave the problem open. Paul Ramsey, hacked up a bit more by me
26 lines
612 B
Makefile
26 lines
612 B
Makefile
# contrib/postgres_fdw/Makefile
|
|
|
|
MODULE_big = postgres_fdw
|
|
OBJS = postgres_fdw.o option.o deparse.o connection.o shippable.o $(WIN32RES)
|
|
PGFILEDESC = "postgres_fdw - foreign data wrapper for PostgreSQL"
|
|
|
|
PG_CPPFLAGS = -I$(libpq_srcdir)
|
|
SHLIB_LINK = $(libpq)
|
|
|
|
EXTENSION = postgres_fdw
|
|
DATA = postgres_fdw--1.0.sql
|
|
|
|
REGRESS = postgres_fdw
|
|
|
|
ifdef USE_PGXS
|
|
PG_CONFIG = pg_config
|
|
PGXS := $(shell $(PG_CONFIG) --pgxs)
|
|
include $(PGXS)
|
|
else
|
|
SHLIB_PREREQS = submake-libpq
|
|
subdir = contrib/postgres_fdw
|
|
top_builddir = ../..
|
|
include $(top_builddir)/src/Makefile.global
|
|
include $(top_srcdir)/contrib/contrib-global.mk
|
|
endif
|