| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | tuanhoanganh <hatuan05(at)gmail(dot)com> |
| Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Rescue data after power off |
| Date: | 2010-07-19 19:16:48 |
| Message-ID: | AANLkTikBWPTcYwDubot9Uh-XnRWszWWZpIJ6vvuIm9ao@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jul 19, 2010 at 5:57 PM, tuanhoanganh <hatuan05(at)gmail(dot)com> wrote:
> I have checked SHOW fsync, It is ON.
> When I view table dmvt on PgAdmin, it only has 1332 rows, but command
> "SELECT count(*) FROM dmvt" return 2449 rows.
By default pgAdmin shows the number of rows listed in pg_class, which
is not always accurate (for all but the smallest of tables).
Right-click the table and select the count options to get an exact
count.
Normally, a large mismatch between those two values is a sign you need
to vacuum the table. That may well not be the case if you're suffering
from corruption though.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sean E. Connolly | 2010-07-19 19:23:41 | Re: NASA needs Postgres - Nagios help |
| Previous Message | Karsten Hilbert | 2010-07-19 18:20:27 | Re: Inheritance and trigger/FK propagation |