| From: | Stephen Robert Norris <srn(at)commsecure(dot)com(dot)au> |
|---|---|
| To: | satish satish <satish_ach2003(at)yahoo(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Data Corruption in case of abrupt failure |
| Date: | 2004-03-16 04:33:31 |
| Message-ID: | 1079411611.2123.4.camel@ws12.commsecure.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2004-03-03 at 23:27, satish satish wrote:
> Hi,
>
> I am trying to do some reliability tests on postgre SQL. I have
> use-case where the power can go off abruptly. I initiated 10,000
> insert operations and pulled out the cable in the middle. I had
> auto-commit option turned on. I observed 2 out of 5 times the tables
> were totally corrupted and could not read any data whereas 3 times I
> was able to read the data which was inserted.
>
> Is there any way that I could avoid that data corruption and ensure
> that atleast the records inserted till that point are available in the
> database. Or are there any tools through which I can recover the data
> in case the database gets corrupted?
>
> Thanks in advance,
> Sathish
>
We'll need more information - what OS and what version of PostgreSQL at
the least.
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-03-16 04:42:14 | Re: Trigger loop question |
| Previous Message | Mike Nolan | 2004-03-16 04:05:15 | Re: Trigger loop question |