placement of stored procedures and contrib modules

From: Michael Gould <mgould(at)intermodalsoftwaresolutions(dot)net>
To: pgsql-sql(at)postgresql(dot)org
Subject: placement of stored procedures and contrib modules
Date: 2010-03-01 13:25:30
Message-ID: 0ca62990c481026fb0a013b7a7ff13d3@intermodalsoftwaresolutions.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

We were trying to use a separate schema to put contrib modules, stored
procedures and triggers from our database schema. We called the one where
we stored all of the modules isscontrib and the other iss which is where the
db is stored. We've fully qualified the names of our items from isscontrib
and have also included that schema in the search path.

Our goal is to eventually mark isscontrib as execute only. Is there any
restrictions to having objects in a separate schema? We are using the
citext contrib module. It doesn't appear to work when it's in the isscontrib
module. We don't get any error messages however we also don't get the
results we are looking for, namely case insensitive search results.

However, if we move the contrib module to the public schema, everything
appears to work fine.

Best Regards

Mike Gould
--
Michael Gould, Managing Partner
Intermodal Software Solutions, LLC
904.226.0978
904.592.5250 fax

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Richard Huxton 2010-03-01 13:38:54 Re: kind of RULE on SELECT depending on existence of a WHERE condition
Previous Message rawi 2010-03-01 12:16:32 Re: kind of RULE on SELECT depending on existence of a WHERE condition