Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id D1A2A6330C0 for ; Mon, 30 Nov 2009 13:53:14 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 55153-05 for ; Mon, 30 Nov 2009 17:53:07 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mail.postgresql.org (Postfix) with ESMTP id 585B16326BA for ; Mon, 30 Nov 2009 13:53:07 -0400 (AST) Received: from list by lo.gmane.org with local (Exim 4.50) id 1NFAQc-000512-Ve for pgsql-sql@postgresql.org; Mon, 30 Nov 2009 18:52:50 +0100 Received: from srv.protecting.net ([212.126.218.242]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Nov 2009 18:52:50 +0100 Received: from hari.fuchs by srv.protecting.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Nov 2009 18:52:50 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-sql@postgresql.org From: Harald Fuchs Subject: Re: Schema's, roles and privileges Date: Mon, 30 Nov 2009 18:51:39 +0100 Lines: 26 Message-ID: References: <803af4645647a59bcb56badac2b1cd8f@intermodalsoftwaresolutions.net> <200911300708.12397.aklaver@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: srv.protecting.net X-Archive: encrypt User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) Cancel-Lock: sha1:DoucFhQ4vWUXExN/enr8oNCLl4U= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 200911/83 X-Sequence-Number: 33434 In article <200911300708.12397.aklaver@comcast.net>, Adrian Klaver writes: > From a quick look it would seem the easiest solution would be to change the > search_path in: > citext.sql.in > uuid-ossp.sql.in > These files are found in the respective contrib directories. Uninstall the > modules. Rerun make and then reinstall. FWIW: I also manage some databases needing one or more contrib/pgfoundry modules. By habit, I install each module in its own schema (with read access to everybody and write access to nobody) - this helps to distinguish between your own DDL and the DDL of helper modules. For example: CREATE SCHEMA prefix; SET search_path = mymodule; \i path_to/mymodule.sql ALTER DATABASE mydb SET search_path = public, mymodule; The SQL files of a few modules mess with the search_path themselves; this can be fixed by editing a copy of .sql and \inserting the copy.