Re: can postgres run well on NFS mounted partitions?
От | Albe Laurenz |
---|---|
Тема | Re: can postgres run well on NFS mounted partitions? |
Дата | |
Msg-id | A737B7A37273E048B164557ADEF4A58B50FE49A5@ntex2010i.host.magwien.gv.at обсуждение исходный текст |
Ответ на | Re: can postgres run well on NFS mounted partitions? (anj patnaik <patna73@gmail.com>) |
Ответы |
Re: can postgres run well on NFS mounted partitions?
|
Список | pgsql-general |
anj patnaik wrote: > How do you tell if a database is corrupted? Are there specific error messages/symptoms to look for? That's actually a pretty tough question. The standard test is to run "pg_dumpall", see if it finishes without error and if the dump can be restored without error. That won't detect any index corruption though. You could try: COPY (SELECT * FROM tab ORDER BY ...) TO 'file1'; SET enable_seqscan=off; COPY (SELECT * FROM tab ORDER BY ...) TO 'file2'; and see if "file1" and "file2" are identical. That would check the index used in the second COPY statement. I don't know, but maybe enabling checksums with the -k option of "initdb" would make such corruption more obvious. Yours, Laurenz Albe
В списке pgsql-general по дате отправления: