From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Christoph Zwerschke *EXTERN*" <cito(at)online(dot)de>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: dblink causing import errors |
Date: | 2012-06-26 13:21:37 |
Message-ID: | D960CB61B694CF459DCFB4B0128514C208127413@exadv11.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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
From | Date | Subject | |
---|---|---|---|
Next Message | David Kerr | 2012-06-26 15:16:32 | Re: Calculating Replication Lag - units |
Previous Message | Tom Lane | 2012-06-26 13:19:55 | Re: txid and current_timestamp |