| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "'Holger(dot)Friedrich-Fa-Trivadis(at)it(dot)nrw(dot)de *EXTERN*'" <Holger(dot)Friedrich-Fa-Trivadis(at)it(dot)nrw(dot)de>, "muthana(dot)al-temimi(at)tu-harburg(dot)hamburg(dot)de" <muthana(dot)al-temimi(at)tu-harburg(dot)hamburg(dot)de>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: database server crash und how can i check all tables |
| Date: | 2015-06-19 11:00:55 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B50F665F0@ntex2010a.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Holger Friedrich wrote:
> Muthana AL-Temimi wrote on Friday, June 19, 2015 12:33 PM:
>> But I want to check all the tables if everything is ok. Is there a command for such problem
>> (check).
> I keep hearing that pgdump is good at detecting database corruption, i.e. if pgdump runs into a
> problem you definitely have corruption. (Not sure if the converse is also true.)
Restoring the dump somewhere else gives you even more confidence in the integrity
of your data.
But if you really want to know if everything is ok, you should have used the "-k"
option for initdb to enable block checksums. Then a pg_dump would definitely tell
you if something is wrong.
Unfortunately checksums can only be enabled at initdb time, not later.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2015-06-19 11:03:06 | Re: database server crash und how can i check all tables |
| Previous Message | Holger.Friedrich-Fa-Trivadis | 2015-06-19 10:45:56 | Re: database server crash und how can i check all tables |