From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Michelle Schwan <mschwan(at)opentext(dot)com> |
Cc: | "pgadmin-support(at)lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pgAdmin IV |
Date: | 2019-06-05 08:30:11 |
Message-ID: | CA+OCxoySXXjFFPOKwdq2F39Ar22Pjq2Lt=w0GiE_x_n+8F-pTQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi
On Tue, Jun 4, 2019 at 3:28 PM Michelle Schwan <mschwan(at)opentext(dot)com> wrote:
> From version pgAdmin IV 4.6 and up, I am now receiving the following error
> message when I import a database into PostgreSQL.
>
>
>
> The database loads fine, but the error that public already exists seems
> strange. Public is the default schema when creating a database – should
> the message just give a warning instead of an error?
>
> Having a Failed (exit code: 1) error makes it seem like the file did not
> load – when in fact it did.
>
> This should be handled better.
>
>
Those errors don't come from pgAdmin - they come from pg_restore (which is
part of PostgreSQL). pgAdmin is just displaying the output it gets from the
tool.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Berg | 2019-06-05 08:38:45 | Re: 4.8 docs build error |
Previous Message | Dave Page | 2019-06-05 08:19:54 | Re: pgAdmin4 4.8 Kubuntu issues |