To: Josh Kupershmidt <schmiddy@gmail.com>
cc: pgsql-docs <pgsql-docs@postgresql.org>
Subject: Re: CREATE EXTENSION: documenting prereqs 
In-reply-to: <BANLkTi=aFRCky-r6ahy50Us2bYpbem8ZcA@mail.gmail.com> 
References: <BANLkTi=aFRCky-r6ahy50Us2bYpbem8ZcA@mail.gmail.com>
Comments: In-reply-to Josh Kupershmidt <schmiddy@gmail.com>
	message dated "Tue, 12 Apr 2011 18:52:12 -0400"
Date: Wed, 13 Apr 2011 03:00:03 -0400
Message-ID: <27761.1302678003@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Josh Kupershmidt <schmiddy@gmail.com> writes:
> Well, obviously I need to go into ./contrib/hstore/ and run make &&
> make install (or install the appropriate -contrib package if I were
> using a packaged build of Postgres). I think it'd be nice to give
> users some hint about this prerequisite. Appendix F [1] discusses
> this, but there's currently no link from [2] to [1]. The way the
> CREATE EXTENSION page reads right now, I could forgive a new user
> thinking he shouldn't need to install any dependencies.

On reflection there are a couple other cross-references that would
be useful here, too.  I've committed a modified version of this.

> A complementary approach would be to add an errhint to the "could not
> open extension control file..." error suggesting that the user install
> the contrib package himself, though I'm not sure offhand about the
> wording, especially since a user might be trying to install
> who-knows-what extension.

Yeah, I'm not sure how to do anything useful in one-or-so-lines there.

			regards, tom lane