head	1.2;
access;
symbols;
locks; strict;
comment	@# @;


1.2
date	2009.02.24.10.06.32;	author petere;	state dead;
branches;
next	1.1;

1.1
date	2008.12.19.16.25.17;	author petere;	state Exp;
branches;
next	;


desc
@@


1.2
log
@Add the possibility to specify an explicit validator function for foreign-data
wrappers (similar to procedural languages).  This way we don't need to retain
the nearly empty libraries, and we are more free in how to implement the
wrapper API in the future.
@
text
@#-------------------------------------------------------------------------
#
# Makefile--
#    Makefile for postgresql foreign-data wrapper
#
# IDENTIFICATION
#    $PostgreSQL: pgsql/src/backend/foreign/postgresql/Makefile,v 1.1 2008/12/19 16:25:17 petere Exp $
#
#-------------------------------------------------------------------------

subdir = src/backend/foreign/postgresql
top_builddir = ../../../..
include $(top_builddir)/src/Makefile.global

NAME = postgresql_fdw
OBJS = postgresql_fdw.o

include $(top_srcdir)/src/Makefile.shlib

all: all-shared-lib

install: all install-lib

installdirs: installdirs-lib

clean distclean maintainer-clean: clean-lib
	rm -f $(OBJS)
@


1.1
log
@SQL/MED catalog manipulation facilities

This doesn't do any remote or external things yet, but it gives modules
like plproxy and dblink a standardized and future-proof system for
managing their connection information.

Martin Pihlak and Peter Eisentraut
@
text
@d7 1
a7 1
#    $PostgreSQL$
@

