| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | yashraj7960(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16601: Restore Issue |
| Date: | 2020-08-28 19:45:38 |
| Message-ID: | CAKFQuwbDviuz43-AFW85k6X6Lp2XH73MthMXBsywZGgQJoU0FQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Aug 28, 2020 at 12:27 PM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 16601
> Logged by: Yash Raj
> Email address: yashraj7960(at)gmail(dot)com
> PostgreSQL version: 13beta3
> Operating system: windows 10
> Description:
>
> I create a database in pgadmin 4 and I'm trying to import the sql file. It
> throws an error like schema public is already exists and i'm unable to run
> the file and create tables with data. Please help me out in this at
> earliest
>
This isn't a bug - future questions of this nature should be sent to either
the -novice or -general lists.
Manually drop the public schema in your created database before restoring
your sql file into it.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-08-28 22:07:30 | Re: BUG #16600: Postgres can't upper lower diacritic character of Croatina alfabet |
| Previous Message | PG Bug reporting form | 2020-08-28 19:04:02 | BUG #16601: Restore Issue |