| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Jim Longwill <JLongwill(at)psmfc(dot)org> |
| Cc: | Jerry Sievers <gsievers19(at)comcast(dot)net>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Error when building new db using pg_restore |
| Date: | 2017-06-21 20:17:06 |
| Message-ID: | CAKFQuwardaaHVbZLX5yreYLJUZkF6VQAVhQ_Z-GD_8xAx-ptYg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jun 21, 2017 at 1:10 PM, Jim Longwill <JLongwill(at)psmfc(dot)org> wrote:
> Given this, I wonder how we can avoid this 'error' situation .. short of
> giving SUPERUSER
> role to rradmin? I tried just removing the '-v' flag from pg_restore,
> but the error is
> still put in the log file (but nothing else is).
I believe the easiest solution, if you can at least get access to
superuser once, is to drop the comment from the source database
altogether. That way it won't be dumped in the first place. I'm not
sure the exact command you need to issue though - just recalling what
I've previously read on the topic.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2017-06-21 20:21:21 | Re: Error when building new db using pg_restore |
| Previous Message | Jim Longwill | 2017-06-21 20:10:18 | Re: Error when building new db using pg_restore |