Re: dblink causing import errors - Mailing list pgsql-general

From Alban Hertroys
Subject Re: dblink causing import errors
Date
Msg-id CAF-3MvPUj44sKDdWA7EF0MUORDc5hovwk0EhwCe5-WR74kXx4Q@mail.gmail.com
Whole thread Raw
In response to dblink causing import errors  (Christoph Zwerschke <cito@online.de>)
List pgsql-general
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.

pgsql-general by date:

Previous
From: Christoph Zwerschke
Date:
Subject: dblink causing import errors
Next
From: Jasen Betts
Date:
Subject: Re: txid and current_timestamp