Re: pg_dump backup issue - Mailing list pgsql-admin

From Erik Serrano
Subject Re: pg_dump backup issue
Date
Msg-id CA+dvXXuudYs3_QYC1MeSwk7mA6X=Q5fnOfF_+-M2w7NhwMGneg@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump backup issue  (M Jane <mskiesewetter@gmail.com>)
List pgsql-admin
Hi Srini,

What pg_dump is telling you is that the table does not exist, if you are still viewing it it is surely still in memory.  Before doing the pg_dump do a vacum parse the table and tell me.

Bye. 

Erik Serrano Saavedra 


El jue., 2 de jul. de 2020 10:04 a. m., M Jane <mskiesewetter@gmail.com> escribió:
Hi Srini,

What version are you running postgres on? What is the command you are running that gives the error?
Have there been any changes prior to the error occurring?

Regards,
Marian

Op do 2 jul. 2020 om 15:12 schreef srini ram <seenuram777@gmail.com>:
Can anyone support me on the blow trial email issue.

Regards,
Srinivasan R

On Mon, 29 Jun 2020, 10:48 pm srini ram, <seenuram777@gmail.com> wrote:
I am facing a problem while performing a pg_dump backup.

I too verified in multiple articles to fix this issue without performing any manual table back and restore, but I couldn't found any easy troubleshooting steps.

Below mentioned are the error message while performing the pg_dump

pg_dump: [archiver (db)] query failed: ERROR:  relation "public.tblraw202012022_p9" does not exist

pg_dump: [archiver (db)] query was: LOCK TABLE public.tblraw202012022_p9 IN ACCESS SHARE MODE


Looks like table is corrupted but still, I couldn't able dop the issue table. If I try to drop the table I am getting a different error response. 


Please help me with the possible solution to fix the above issue.

Thanks&Regards,
Srinivasan R
Ph.,:9035911976

pgsql-admin by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: how to conveniently upgrade with specific catalog change
Next
From: Wells Oliver
Date:
Subject: native solutions for copying data between PG servers?