On Wed, Oct 12, 2011 at 10:50 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Andrew Dunstan <and...@dunslane.net> writes: >> *shrug* ok. Another thought I had was to have the file raise an error >> and have that filtered out by the extension mechanism. But I'm not sure >> if it's worth the trouble. > > Hmm ... > > \echo You should use CREATE EXTENSION foo to load this file! > > and teach CREATE EXTENSION to drop any line beginning with \echo? > The latter part seems easy enough, but I'm not quite sure about the > wording or placement of the \echo command. Putting it at the top > feels natural but the message might scroll offscreen due to errors...
Decorate them with a marker like: \extension <name> <version> And make the CREATE EXTENSION skip (or verify) it? It will make psql stop on the \extension command. a. -- Aidan Van Dyk Create like a god, ai...@highrise.ca command like a king, http://www.highrise.ca/ work like a slave. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
