contrib/README

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>
Subject: contrib/README
Date: 2011-12-26 22:56:13
Message-ID: 1324940000-sup-2881@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Apparently we forgot to update the README file in contrib/. I wonder if
it's necessary to explain that within each directory you find one or
more ".control" file that determines what can be run ... or maybe just
mention the pg_extensions views?

What about this?

diff --git a/contrib/README b/contrib/README
index a1d42a1..8900693 100644
--- a/contrib/README
+++ b/contrib/README
@@ -11,11 +11,11 @@ User documentation for each module appears in the main SGML documentation.
Most items can be built with `gmake all' and installed with
`gmake install' in the usual fashion, after you have run the `configure'
script in the top-level directory. Some directories supply new
-user-defined functions, operators, or types. In these cases, after you have
+user-defined Postgres extensions. In these cases, after you have
installed the files you need to register the new entities in the database
-system by running the commands in the supplied .sql file. For example,
+system by running an appropriate CREATE EXTENSION command. For example,

- $ psql -d dbname -f module.sql
+ $ psql -d dbname -c "CREATE EXTENSION pg_trgm"

See the PostgreSQL documentation for more information about this
procedure.

--
Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2011-12-26 23:00:00 Re: Adding XSLT support to PostgreSQL core?
Previous Message Magnus Hagander 2011-12-26 17:32:42 Re: Standalone synchronous master