Thanks for your reply.
this is happening when system starts copying data for the biggest table, so just to reconfirm I have taken a pg_dump with Fp for that single table and tried to restore the same into PG cluster which was successful, and then again when I tried to restore the complete cluster dump taken using pg_dumpall it failed again.
cloud=# \d+ t_3ecc35f89a0c485eb365744bde452408.jx_objectstore_journal
Table "t_3ecc35f89a0c485eb365744bde452408.jx_objectstore_journal"
Column | Type | Modifiers | Storage | Stats target | Description
----------------+-----------------------------+-----------+----------+--------------+-------------
did | integer | not null | plain | |
start | timestamp without time zone | not null | plain | |
ending | timestamp without time zone | not null | plain | |
deltas | text | | extended | |
deltacount | integer | | plain | |
finalstate | text | | extended | |
measure_start | timestamp without time zone | | plain | |
measure_ending | timestamp without time zone | | plain | |
Indexes:
"jx_objectstore_journal_pkey" PRIMARY KEY, btree (did, start, ending)
"idx_jx_objectstore_journal_did" btree (did)
"idx_jx_objectstore_journal_ending" btree (ending)
"idx_jx_objectstore_journal_start" btree (did, start)
Has OIDs: no
Actual table size is around 2GB and toast table size is 288 GB which might have around 80 GB of dead rows.