BUG #15235: Getting failure message "Restore archive operation failed" while restoring database

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

BUG #15235: Getting failure message "Restore archive operation failed" while restoring database

PG Bug reporting form
The following bug has been logged on the website:

Bug reference:      15235
Logged by:          Prasad M
Email address:      [hidden email]
PostgreSQL version: 9.6.0
Operating system:   Microsoft Windows 2012 R2 Server
Description:        

Restore archive operation failed: - System.Exception: pg_restore: connecting
to database for restore
pg_restore: processing item 2595 ENCODING ENCODING
pg_restore: processing item 2596 STDSTRINGS STDSTRINGS
.....
....
pg_restore: processing data for table "Table1"
pg_restore: [archiver (db)] error returned by PQputCopyData: could not send
data to server: Software caused connection abort (0x00002745/10053)
pg_restore: [archiver (db)] error returned by PQputCopyData: could not send
data to server: Software caused connection abort (0x00002745/10053)
pg_restore: [archiver (db)] error returned by PQputCopyData: could not send
data to server: Software caused connection abort (0x00002745/10053)
pg_restore: [parallel archiver] a worker process died unexpectedly
pg_restore: [archiver (db)] Error while PROCESSING TOC:

Reply | Threaded
Open this post in threaded view
|

Re: BUG #15235: Getting failure message "Restore archive operation failed" while restoring database

Jeff Janes
On Sat, Jun 9, 2018 at 6:01 AM, PG Bug reporting form <[hidden email]> wrote:
The following bug has been logged on the website:

Bug reference:      15235
Logged by:          Prasad M
Email address:      [hidden email]
PostgreSQL version: 9.6.0
Operating system:   Microsoft Windows 2012 R2 Server
Description:       

Restore archive operation failed: - System.Exception: pg_restore: connecting
to database for restore
pg_restore: processing item 2595 ENCODING ENCODING
pg_restore: processing item 2596 STDSTRINGS STDSTRINGS
.....
....
pg_restore: processing data for table "Table1"
pg_restore: [archiver (db)] error returned by PQputCopyData: could not send
data to server: Software caused connection abort (0x00002745/10053)
pg_restore: [archiver (db)] error returned by PQputCopyData: could not send
data to server: Software caused connection abort (0x00002745/10053)
pg_restore: [archiver (db)] error returned by PQputCopyData: could not send
data to server: Software caused connection abort (0x00002745/10053)
pg_restore: [parallel archiver] a worker process died unexpectedly
pg_restore: [archiver (db)] Error while PROCESSING TOC:


What does the postgresql server log file say?

Cheers,

Jeff
Reply | Threaded
Open this post in threaded view
|

Re: BUG #15235: Getting failure message "Restore archive operation failed" while restoring database

Tom Lane-2
In reply to this post by PG Bug reporting form
=?utf-8?q?PG_Bug_reporting_form?= <[hidden email]> writes:
> PostgreSQL version: 9.6.0
> ...
> pg_restore: [parallel archiver] a worker process died unexpectedly

If this is really 9.6.0, your first move should be to update to
current (9.6.9, at present) to see if the problem is already fixed.

                        regards, tom lane

Reply | Threaded
Open this post in threaded view
|

BUG #15235: Getting failure message "Restore archive operation failed" while restoring database

Matkar, Prasad L (BHGE)
Hello Tom,

We tried with PostgreSql 9.6.9 but it does not help solve my issue.
Let me know if you can help on this.

Regards,
Prasad Matkar

-----Original Message-----
From: Tom Lane [mailto:[hidden email]]
Sent: Saturday, June 09, 2018 9:37 PM
To: Matkar, Prasad L (BHGE) <[hidden email]>
Cc: [hidden email]
Subject: EXT: Re: BUG #15235: Getting failure message "Restore archive operation failed" while restoring database

=?utf-8?q?PG_Bug_reporting_form?= <[hidden email]> writes:
> PostgreSQL version: 9.6.0
> ...
> pg_restore: [parallel archiver] a worker process died unexpectedly

If this is really 9.6.0, your first move should be to update to current (9.6.9, at present) to see if the problem is already fixed.

                        regards, tom lane

Reply | Threaded
Open this post in threaded view
|

Re: BUG #15235: Getting failure message "Restore archive operation failed" while restoring database

Tom Lane-2
"Matkar, Prasad L (BHGE)" <[hidden email]> writes:
> We tried with PostgreSql 9.6.9 but it does not help solve my issue.
> Let me know if you can help on this.

OK, in that case we're going to need you to extract a self-contained
test case for us to poke at.

If you don't want to do that, you could look into the postmaster log
to see if it offers any more hints about what happened, or you could
see if there's a core file to try to extract a stack trace from.
But we can't really promise that we can figure it out without a
test case.

                        regards, tom lane

Reply | Threaded
Open this post in threaded view
|

BUG #15235: Getting failure message "Restore archive operation failed" while restoring database

Matkar, Prasad L (BHGE)
Hello Tom,

We reset the number of Parallel job from 5 to 1, the pgrestore is successful however too slow.
Please let me know if there is anything to improve upon the pgrestore time.

Regards,
Prasad Matkar

-----Original Message-----
From: Tom Lane [mailto:[hidden email]]
Sent: Wednesday, June 13, 2018 8:38 PM
To: Matkar, Prasad L (BHGE) <[hidden email]>
Cc: [hidden email]
Subject: EXT: Re: BUG #15235: Getting failure message "Restore archive operation failed" while restoring database

"Matkar, Prasad L (BHGE)" <[hidden email]> writes:
> We tried with PostgreSql 9.6.9 but it does not help solve my issue.
> Let me know if you can help on this.

OK, in that case we're going to need you to extract a self-contained test case for us to poke at.

If you don't want to do that, you could look into the postmaster log to see if it offers any more hints about what happened, or you could see if there's a core file to try to extract a stack trace from.
But we can't really promise that we can figure it out without a test case.

                        regards, tom lane