| From: | "Mario Weilguni" <mweilguni(at)sime(dot)com> |
|---|---|
| To: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Data files became huge with no apparent reason |
| Date: | 2002-08-28 10:44:14 |
| Message-ID: | 01d901c24e7f$da683230$6f01c00a@icomedias.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> I'm returned from a 2 weeks vacation and I'm now facing a problem that
> is effectively blocking a critical database server.
>
[snip]
> - And last, but not least... is it possible to restore the situation
> without loosing data (backup is 3 weeks old)? I'm able to start the
not having a daily backup for a critical database server is no good idea, no
matter how stable a database is. think of a hardware crash.
some ideas:
1.first you should try to make a filesystem backup of your database. that
means, stop the database, make a tar file of your data directory, and
restart the database. so you'll have a chance to recover in case your rescue
efforts make things worse.
2. use "vacuum verbose" and remember the location where vacuum crashes. this
will make tracking down the error easier.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michał Kalański | 2002-08-28 10:49:48 | psql 7.2.1 on S/390 |
| Previous Message | Christian Mock | 2002-08-28 10:38:21 | Re: stupid Q regarding "UPDATE waiting" |