| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Phui Hock <phuihock(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: How to inherit search_path from template |
| Date: | 2010-09-13 12:30:38 |
| Message-ID: | AANLkTimxa2+zJ3_s9yWyRb_CD4JFB5Wb=qWU+zsP-6U6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Sep 12, 2010 at 8:34 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Thu, Sep 9, 2010 at 7:41 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
>> On Thu, Sep 9, 2010 at 7:13 AM, Phui Hock <phuihock(at)gmail(dot)com> wrote:
>>> Hi,
>>> How can I create a database template with altered search_path to be
>>> inherited by child databases? Say, I created a template named
>>> template_a with the following commands:
>>
>> It doesn't really work that way -- GUC values are global, not per
>> database.
>
> You can do "alter database xyz set search_path=..."
so you can...thanks for that!
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rob Richardson | 2010-09-13 12:59:06 | Re: Is there a bug in FOR i IN 1..10 LOOP (8.4.4)? |
| Previous Message | MailingLists | 2010-09-13 11:48:50 | new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII) |