dblink causing import errors

On 26 June 2012 10:59, Christoph Zwerschke <cito@online.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.

Christoph Zwerschke 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?

In version 9.0 and below you pretty much have to live with that.

From 9.1 on, you install dblink with CREATE EXTENSION, and things
should get better. You can create the extension in the template
database and should not get any more errors when you restore
a dump that already contains the extension.

Yours,
Laurenz Albe