| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org> |
| Subject: | Re: Contrib Schemas |
| Date: | 2006-01-13 01:11:39 |
| Message-ID: | 200601121711.40132.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom,
> People who want the contrib stuff segregated can easily make it
> happen by modifying the contrib .sql files before they run them.
> The .sql files already have a skeleton for this, eg
> -- Adjust this setting to control where the objects get created.
> SET search_path = public;
> I don't really see a need to go further than that.
Tangentally, I filed a but with Tsearch2 because that SET statement is
outside the transaction in the .sql file, which means that stuff will end
up in the public schema if the admin typos the schema name. Not sure if
other contrib modules have the same issue.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John DeSoi | 2006-01-13 01:14:42 | info is a reserved word? |
| Previous Message | Tom Lane | 2006-01-13 00:33:37 | Re: Contrib Schemas |