From: | Alban Hertroys <haramrae(at)gmail(dot)com> |
---|---|
To: | Christoph Zwerschke <cito(at)online(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: dblink causing import errors |
Date: | 2012-06-26 10:04:06 |
Message-ID: | CAF-3MvPUj44sKDdWA7EF0MUORDc5hovwk0EhwCe5-WR74kXx4Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 26 June 2012 10:59, Christoph Zwerschke <cito(at)online(dot)de> wrote:
> Our developers like the dblink modules, so I have installed it into the
> template1 database. They also like to import old database dumps after
> creating new databases with dbcreate. But then they get irritated by the
> error messages saying that the dblink functions already exist, because these
> functions are in the old dumps, but dbcreate already copied them from the
> template1 database. Also, some scripts which copy databases break or create
> unnecessary error messages because of that. Are there any best practices
> when using dblink to avoid these issues?
I usually create a new template database containing such functions and
use that template in the CREATE DATABASE statements.
--
If you can't see the forest for the trees,
Cut the trees and you'll see there is no forest.
From | Date | Subject | |
---|---|---|---|
Next Message | Jasen Betts | 2012-06-26 10:20:25 | Re: txid and current_timestamp |
Previous Message | Christoph Zwerschke | 2012-06-26 08:59:58 | dblink causing import errors |