Tom Lane 458857cc9d 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
..
autoinc--1.0.sql
autoinc--unpackaged--1.0.sql
autoinc.c
autoinc.control
autoinc.example
insert_username--1.0.sql
insert_username--unpackaged--1.0.sql
insert_username.c
insert_username.control
insert_username.example
Makefile
moddatetime--1.0.sql
moddatetime--unpackaged--1.0.sql
moddatetime.c
moddatetime.control
moddatetime.example
refint--1.0.sql
refint--unpackaged--1.0.sql
refint.c
refint.control
refint.example
timetravel--1.0.sql
timetravel--unpackaged--1.0.sql
timetravel.c
timetravel.control
timetravel.example