On Tue, Jun 15, 2010 at 19:02, Brad Nicholson <bnichols@ca.afilias.info> wrote:
> I want to put the functions from pgcrypto into a separate schema, but
> pgcrypto.sql is explicitly setting the search path to public. Is there
> a reason it does this that I should be aware of? Is it fine to change
> that and install the functions in a separate schema?
Nope, just remove that line. pgcrypto works perfectly fine when
running in it's own schema - in fact, I think that's the general
recommendation. I think the lock to public schema was just left in
there pending the extensions mechanism to eventually get finished.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
