Hello Adrian,
> Then I am of no further use to this conversation.
No problem at all.
Thank you for your well considered input and ideas.
Have a lovely day.
Kindest regards,
Tomas
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
ht
Hello Karsten,
> In that case I must surely have missed it and feel I
> can no longer be of any assistance, even if it only
> amounted to but contributing leads to be investigated.
> Sorry.
No problem at all.
I very much appreciate all your input and ideas.
Thank you.
Kindest regards,
Toma
Hello Karsten,
Thank you.
> Like replacing (some of) the pg_* containing raw files with
> those from an uncorrupted database (having been suggested
> earlier this year) which may work if the corrupted blocks in
> pg_* only affect data actually describing _that_ database
> rather than establis
Hello Andrian,
Thank you
> Have you even tried a schema only dump from the original instance?
That's an odd question. However, I understand that maybe a lot of beginners
come onto this mailing list.
To the contrary, this is a non-trivial situation.
You can safely assume that I wrote the origin
Hello Karsten,
Thank you.
> I believe Adrian wanted to know whether you attempted a
> schema or complete dump *after* the fact, like what he
> suggested a mail ago or so.
>
> In case the FS corruption "only" affects raw files related to
> user data (as opposed to also affecting data in pg_*
Hello Karsten,
> If I recall correctly, you stated that the data isn't
> important in this
Yes, exactly. However, pages in blocks apparently store also the
representations of the database schemas. And those are also corrupt.
A tiny bit only but still corrupt.
Therefore the overall information
Hello Adrian,
Thank you.
> So did you do a schema only dump or a complete dump?
There is no dump. There are just raw files.
> Well if the corrupted raw files include the system information
> then I think you are out of luck.
Well, this topic is not about "luck".
The question potentially ta
Hello Melvin,
Thank you.
Your reply is similar to the first one in that it makes assumptions to the
contrary of my original e-mail.
Therefore I shall tackle only the relevant bits:
1. This is not related to any existing bug. It was a corruption of the file
system.
2. OID of the corrupt databas
Please note that I mentioned previously that the database is corrupt.
"pg_class" table can be queried but it is not possible to dump the database
in question as some of the pages in blocks are missing.
In this case, it is necessary to rely on raw files only. Thanks.
T
--
Sent via pgsql-gener
Hello Adrian,
> So to be clear, all that remains of the database cluster are the files
> you copied out from the data directory, correct?
Yes and no. For the purpose of this discussion, it may be better to say "yes"
though.
> That would imply that the server actually started, is that the case?
Hello Venkata,
Thank you for your reply.
You are stating the obvious though. If those conditions were met, I would have
formulated my question differently.
Kind regards,
Tomas
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http:/
Hello,
There was a corruption to the file system due to sudden shutdown of Windows
7.
The attempt to connect to one of the databases results in multiple errors,
like the following one:
ERROR: invalid page in block 58 of relation base/161326/233745
Several raw files were completely lost (zeroed)
12 matches
Mail list logo
