On Wed, 2006-09-13 at 10:05, Alban Hertroys wrote:
> Berend Tober wrote:
> > On Wed, Sep 13, 2006 at 10:56:41AM +0200, Alban Hertroys wrote:
> >
> > 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.
>
>
On 2006-09-13, Alban Hertroys <[EMAIL PROTECTED]> wrote:
> I'm quite certain that approach can be made more bullet-proof by
> wrapping it inside a transaction. I saw no mention of that on his page.
>
> It's quite amazing what PostgreSQL can handle inside transactions :)
Some of the few things tha
Berend Tober wrote:
On Wed, Sep 13, 2006 at 10:56:41AM +0200, Alban Hertroys wrote:
>
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.
I'm quite certain that approach can be made more bullet-proof by
wr
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/pgsqladventure
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/pgsqladv
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
