Re: CREATE EXTENSION: documenting prereqs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
Cc: pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: CREATE EXTENSION: documenting prereqs
Date: 2011-04-13 07:00:03
Message-ID: 27761.1302678003@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Josh Kupershmidt <schmiddy(at)gmail(dot)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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Daniele Varrazzo 2011-04-13 10:31:45 Proposal: syntax highlight in html manual
Previous Message Josh Kupershmidt 2011-04-12 22:52:12 CREATE EXTENSION: documenting prereqs