mirror of
https://github.com/postgres/postgres.git
synced 2025-10-31 00:03:57 -04:00
458857cc9d
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.
11 lines
559 B
SQL
11 lines
559 B
SQL
/* contrib/test_parser/test_parser--unpackaged--1.0.sql */
|
|
|
|
-- complain if script is sourced in psql, rather than via CREATE EXTENSION
|
|
\echo Use "CREATE EXTENSION test_parser" to load this file. \quit
|
|
|
|
ALTER EXTENSION test_parser ADD function testprs_start(internal,integer);
|
|
ALTER EXTENSION test_parser ADD function testprs_getlexeme(internal,internal,internal);
|
|
ALTER EXTENSION test_parser ADD function testprs_end(internal);
|
|
ALTER EXTENSION test_parser ADD function testprs_lextype(internal);
|
|
ALTER EXTENSION test_parser ADD text search parser testparser;
|