| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "poonam(dot)joon(at)fosteringlinux(dot)com" <poonam(dot)joon(at)fosteringlinux(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15898: pg_dump error not able to restore complete dump |
| Date: | 2019-07-06 07:41:42 |
| Message-ID: | CAKFQuwZFvEZJhzEv+V2dFGwCXSmEQxVdXLb=N=y2riWicQAc6Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Friday, July 5, 2019, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 15898
> Logged by: Poonam Joon
> Email address: poonam(dot)joon(at)fosteringlinux(dot)com
> PostgreSQL version: 10.9
> Operating system: Rhel 7.1
> Description:
>
> Why we are getting an error while restoring the pg_dump data from postgres
> 10.4 to 10.9 version.
> Even when we are restoring data then only some tables are restoring not
> all.
> All backup types like gz,.sql and binary backup are also making the error.
> Why these formats are not supporting in all tables back up.
>
You need to show at least the commands you are running and the errors that
are coming up. Showing the original pg_dump command is useful too.
And it would be helpful to do that on the -general email list as this is
not a bug and thus does not belong on the bug reporting list.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2019-07-06 13:11:18 | Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)« |
| Previous Message | Manuel Rigger | 2019-07-05 23:36:21 | Re: ALTER TABLE SET WITH OIDS fails after failed CONCURRENTLY index creation |