From: | "Harald Armin Massa" <haraldarminmassa(at)gmail(dot)com> |
---|---|
To: | "General Postgres Mailing List" <pgsql-general(at)postgresql(dot)org> |
Subject: | how can I exclude stuff from template in my dumps? |
Date: | 2008-11-18 15:04:11 |
Message-ID: | 7be3f35d0811180704p2a40a1b9k66b816be1a6dd392@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
hello,
on restoring dumps I get errors about languages and functions not
getting restored:
pg_restore: [Archivierer (DB)] Fehler in Inhaltsverzeichniseintrag 135; 1255 164
39 FUNCTION pldbg_step_over(integer) postgres
pg_restore: [Archivierer (DB)] could not execute query: FEHLER: Funktion »pldb
g_step_over« existiert bereits mit den selben Argumenttypen
Command was: CREATE FUNCTION pldbg_step_over(session integer) RETURNS breakp
oint
AS '$libdir/pldbgapi', 'pldbg_step_over'
LANGUAG...
of course ... pldbpg_step_over is allready present, as it is installed
by the setup of the template database and thatfore it is on every
database.
Same with procedural language pl/pgsql and pg_buffercache etc...
Result: pg_restore ignores 29 errors, which is harmless, as those
functions are allready present.
BUT: it would be nicer, to not have these errors, as they can
overshaddow REAL error messages within the output.
Is there a clever way to exclude them from dumps or restores?
Harald
--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
no fx, no carrier pigeon
-
EuroPython 2009 will take place in Birmingham - Stay tuned!
From | Date | Subject | |
---|---|---|---|
Next Message | tv | 2008-11-18 15:06:16 | Re: Slow queries when ORDER BY ... DESC with table inheritance (no index scan backwards) |
Previous Message | Stephane Bortzmeyer | 2008-11-18 15:01:59 | Re: Urgent - Grant |