| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kynn Jones" <kynnjo(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Vacuous errors in pg_dump ... | pg_restore pipeline |
| Date: | 2008-02-20 20:14:23 |
| Message-ID: | 15475.1203538463@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Kynn Jones" <kynnjo(at)gmail(dot)com> writes:
> As far as the shell is concerned, this pipeline fails, due to three errors
> emitted by pg_restore. All these errors are vacuous, as far as I can tell.
They're hardly vacuous --- they're telling you that the destination
database will be missing plpgsql, which was in the source database.
The only really good way around that pre-8.3 is to run the restore as
a database superuser. As of 8.3 it should be sufficient to be the
database's owner.
If you don't have any actual use for plpgsql in this database, maybe
you should remove it from the source DB?
> BTW, while on this subject: is there a way to modify the pipeline above to
> minimize the number of warnings and notices generated during pg_restore?
... | PGOPTIONS="--client_min_messages=warning" pg_restore ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michelle Konzack | 2008-02-20 20:55:04 | /var/lib/postgres on Hitachi E5K160 60 GByte (Raid-1 + Hotfix) |
| Previous Message | brian | 2008-02-20 19:58:32 | Re: Suggestions for schema design? |