Re: can postgres run well on NFS mounted partitions? - Mailing list pgsql-general

From Melvin Davidson
Subject Re: can postgres run well on NFS mounted partitions?
Date
Msg-id CANu8Fiwd+-NovU=UY3GOWJT4+7QJaAY8MW+j3g1+8TDproODKg@mail.gmail.com
Whole thread Raw
In response to Re: can postgres run well on NFS mounted partitions?  (Albe Laurenz <laurenz.albe@wien.gv.at>)
List pgsql-general
Another good idea is to do a

grep FATAL: your_postgres_log

and see if PostgreSQL is complaining about anything relating to table. index or WAL access,
otherwise, usually the only "acceptable" FATAL's are related to pg_hba.conf authorization or other connection
problems.

On Mon, Nov 16, 2015 at 3:43 AM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
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

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



--
Melvin Davidson
I reserve the right to fantasize.  Whether or not you
wish to share my fantasy is entirely up to you.

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: DB_link connection
Next
From: Johannes
Date:
Subject: update inside function does not use the index