| From: | Berend Tober <btober(at)seaworthysys(dot)com> |
|---|---|
| To: | Alban Hertroys <alban(at)magproductions(dot)nl> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Template1 oops |
| Date: | 2006-09-13 14:41:21 |
| Message-ID: | 45081891.5050803@seaworthysys.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Sep 13, 2006 at 10:56:41AM +0200, Alban Hertroys wrote:
>>I found an oops in one of our template1 databases; tables and stuff were
>>apparently loaded into the wrong database (namely template1). I found
>>this page describing a solution:
>>http://techdocs.postgresql.org/techdocs/pgsqladventuresep1.php
>>
>>But, this looks kind of risky to me. I'd prefer not to put our running
>>databases at risk.
>>
>>As an alternative approach, wouldn't dropping and recreating the public
>>schema be a nice alternative? And in that case, what would be the right
>>CREATE SCHEMA public command? I don't feel like messing this up ;)
>>
>>
I'm humble (or naive) enough to admit that I've used the approach
outlined there by Josh Berkus, and it worked fine. More than once, even.
Regards,
BMT
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2006-09-13 15:05:40 | Re: Template1 oops |
| Previous Message | Fabi Avilés | 2006-09-13 14:39:34 | Problems with date configuration |