pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedby mistake dropped physical file dropped for one table.
3+ messages / 2 participants
[nested] [flat]
* by mistake dropped physical file dropped for one table.
@ 2018-03-06 11:35 Rambabu V <ram.wissen@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Rambabu V @ 2018-03-06 11:35 UTC (permalink / raw)
To: pgsql-performance
Hi Team,
by mistake one physical file dropped for one of our table, as we do-not
have backup for this table we are getting below error.
ERROR: could not open file "base/12669/16394": No such file or directory
please help us to recover the table.
Regards,
Rambabu Vakada,
PostgreSQL DBA.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: by mistake dropped physical file dropped for one table.
@ 2018-03-06 13:21 Stephen Frost <sfrost@snowman.net>
parent: Rambabu V <ram.wissen@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Frost @ 2018-03-06 13:21 UTC (permalink / raw)
To: Rambabu V <ram.wissen@gmail.com>; +Cc: pgsql-performance
Greetings,
* Rambabu V (ram.wissen@gmail.com) wrote:
> by mistake one physical file dropped for one of our table, as we do-not
> have backup for this table we are getting below error.
>
> ERROR: could not open file "base/12669/16394": No such file or directory
>
> please help us to recover the table.
You're not likely able to recover that table. To do so would require
completely stopping the system immediately and attempting to perform
filesystem maniuplation to "undelete" the file, or pull back chunks from
the filesystem which contain pieces of the file and attempting to
reconstruct it.
If you've been keeping all WAL since the beginning of the cluster, it's
possible you could recover that way, but you claim to not have any
backups, so I'm guessing that's pretty unlikely.
Thanks!
Stephen
Attachments:
[application/pgp-signature] signature.asc (818B, ../../20180306132124.GL2416@tamriel.snowman.net/2-signature.asc)
download
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: by mistake dropped physical file dropped for one table.
@ 2018-03-06 13:27 Rambabu V <ram.wissen@gmail.com>
parent: Stephen Frost <sfrost@snowman.net>
0 siblings, 0 replies; 3+ messages in thread
From: Rambabu V @ 2018-03-06 13:27 UTC (permalink / raw)
To: Stephen Frost <sfrost@snowman.net>; +Cc: pgsql-performance
Ok, thanks.
On Mar 6, 2018 6:51 PM, "Stephen Frost" <sfrost@snowman.net> wrote:
> Greetings,
>
> * Rambabu V (ram.wissen@gmail.com) wrote:
> > by mistake one physical file dropped for one of our table, as we do-not
> > have backup for this table we are getting below error.
> >
> > ERROR: could not open file "base/12669/16394": No such file or directory
> >
> > please help us to recover the table.
>
> You're not likely able to recover that table. To do so would require
> completely stopping the system immediately and attempting to perform
> filesystem maniuplation to "undelete" the file, or pull back chunks from
> the filesystem which contain pieces of the file and attempting to
> reconstruct it.
>
> If you've been keeping all WAL since the beginning of the cluster, it's
> possible you could recover that way, but you claim to not have any
> backups, so I'm guessing that's pretty unlikely.
>
> Thanks!
>
> Stephen
>
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2018-03-06 13:27 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-03-06 11:35 by mistake dropped physical file dropped for one table. Rambabu V <ram.wissen@gmail.com>
2018-03-06 13:21 ` Stephen Frost <sfrost@snowman.net>
2018-03-06 13:27 ` Rambabu V <ram.wissen@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox