| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "'anj patnaik *EXTERN*'" <patna73(at)gmail(dot)com>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: can postgres run well on NFS mounted partitions? |
| Date: | 2015-11-16 08:43:36 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B50FE49A5@ntex2010i.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Geoff Winkless | 2015-11-16 10:30:18 | referencing other INSERT VALUES columns inside the insert |
| Previous Message | Tim Uckun | 2015-11-16 06:52:12 | Re: Importing directly from BCP files |