| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | codeWarrior <gpatnude(at)hotmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Urgent! |
| Date: | 2005-10-13 16:21:24 |
| Message-ID: | 1129220484.29961.191.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, 2005-10-13 at 10:56, Bruce Momjian wrote:
> codeWarrior wrote:
> > Lookas as if you've managed to turn off your computer mid-transaction
> > thereby corrupting the postgreSQL commit logs (pg_clog)...
> >
> > You should never just turn off a database server... always shut it down
> > normally... Turning it off was a major mistake. I dont know if you can
> > recover or not as the system (postgreSQL) now thinks it is in the middle of
> > a transaction...
>
> PostgreSQL should never get corrupted by turning off the server. It
> isn't ideal to do that, but it should not get corrupted.
Unless it is installed on hardware that lies about fsync.
Which almost all ATA drives, parallel and serial, do, sadly.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-10-13 16:23:44 | Re: Urgent! |
| Previous Message | Alvaro Herrera | 2005-10-13 16:12:50 | Re: Urgent! |