postgresql/contrib/file_fdw/file_fdw--1.0.sql

/* contrib/file_fdw/file_fdw--1.0.sql */

-- complain if script is sourced in psql, rather than via CREATE EXTENSION
\echo Use "CREATE EXTENSION file_fdw" to load this file. \quit

CREATE FUNCTION file_fdw_handler()
RETURNS fdw_handler
AS 'MODULE_PATHNAME'
LANGUAGE C STRICT;

CREATE FUNCTION file_fdw_validator(text[], oid)
RETURNS void
AS 'MODULE_PATHNAME'
LANGUAGE C STRICT;

CREATE FOREIGN DATA WRAPPER file_fdw
  HANDLER file_fdw_handler
  VALIDATOR file_fdw_validator;
Add contrib/file_fdw foreign-data wrapper for reading files via COPY. This is both very useful in its own right, and an important test case for the core FDW support. This commit includes a small refactoring of copy.c to expose its option checking code as a separately callable function. The original patch submission duplicated hundreds of lines of that code, which seemed pretty unmaintainable. Shigeru Hanada, reviewed by Itagaki Takahiro and Tom Lane 2011-02-20 14:06:59 -05:00			`/* contrib/file_fdw/file_fdw--1.0.sql */`

Throw a useful error message if an extension script file is fed to psql. We have seen one too many reports of people trying to use 9.1 extension files in the old-fashioned way of sourcing them in psql. Not only does that usually not work (due to failure to substitute for MODULE_PATHNAME and/or @extschema@), but if it did work they'd get a collection of loose objects not an extension. To prevent this, insert an \echo ... \quit line that prints a suitable error message into each extension script file, and teach commands/extension.c to ignore lines starting with \echo. That should not only prevent any adverse consequences of loading a script file the wrong way, but make it crystal clear to users that they need to do it differently now. Tom Lane, following an idea of Andrew Dunstan's. Back-patch into 9.1 ... there is not going to be much value in this if we wait till 9.2. 2011-10-12 15:45:03 -04:00			`-- complain if script is sourced in psql, rather than via CREATE EXTENSION`
			`\echo Use "CREATE EXTENSION file_fdw" to load this file. \quit`

Add contrib/file_fdw foreign-data wrapper for reading files via COPY. This is both very useful in its own right, and an important test case for the core FDW support. This commit includes a small refactoring of copy.c to expose its option checking code as a separately callable function. The original patch submission duplicated hundreds of lines of that code, which seemed pretty unmaintainable. Shigeru Hanada, reviewed by Itagaki Takahiro and Tom Lane 2011-02-20 14:06:59 -05:00			`CREATE FUNCTION file_fdw_handler()`
			`RETURNS fdw_handler`
			`AS 'MODULE_PATHNAME'`
			`LANGUAGE C STRICT;`

			`CREATE FUNCTION file_fdw_validator(text[], oid)`
			`RETURNS void`
			`AS 'MODULE_PATHNAME'`
			`LANGUAGE C STRICT;`

			`CREATE FOREIGN DATA WRAPPER file_fdw`
			`HANDLER file_fdw_handler`
			`VALIDATOR file_fdw_validator;`