Re: BUG #15898: pg_dump error not able to restore complete dump - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #15898: pg_dump error not able to restore complete dump
Date
Msg-id CAKFQuwZFvEZJhzEv+V2dFGwCXSmEQxVdXLb=N=y2riWicQAc6Q@mail.gmail.com
Whole thread Raw
In response to BUG #15898: pg_dump error not able to restore complete dump  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Friday, July 5, 2019, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      15898
Logged by:          Poonam Joon
Email address:      poonam.joon@fosteringlinux.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.

pgsql-bugs by date:

Previous
From: Manuel Rigger
Date:
Subject: Re: ALTER TABLE SET WITH OIDS fails after failed CONCURRENTLY index creation
Next
From: Christoph Berg
Date:
Subject: Re: BUG #15896: pg_upgrade from 10-or-earlier: TRAP: FailedAssertion(»!(metad->btm_version >= 3)«