Skip site navigation (1) Skip section navigation (2)

[Q] post-crash behaviour

From: Fabien COUTANT <Fabien(dot)Coutant(at)steria(dot)fr>
To: pgsql-docs(at)postgresql(dot)org
Subject: [Q] post-crash behaviour
Date: 2001-03-05 17:29:55
Message-ID: 20010305182954.A13365@etisrv (view raw, whole thread or download thread mbox)
Lists: pgsql-docs
I don't know if this the right place to post this, please excuse me if
I'm wrong.  I didn't find any clearly appropriate E-mail for this on the

I'm working on a project where we are questionning ourselves about the
reliability of PostgreSQL (our customer wants to compare to Oracle but
it's no matter for my question).

Our main concern is databases files' internal structure corruption. 
What is PostgreSQL's behaviour regarding software and hardware failures:
- soft termination of the server (kill -INT),
- hard termination (kill -9, server bug),
- power loss (or disk failure) that occurs in the middle of disk I/O,

I searched the docs and found nothing about this.  I also searched
newsgroups with no success.

I would like to know if, in those cases:
- is the server able to restart and operate correctly on correct data
  (transaction wise) ?
- if internal file corruption could occur, would the server tell on
  startup something like "The database is corrupted, can't start" ?
  And this in a deterministic way ?
- or is there a risk that the server could start and run with corrupted
  files and data ?

Thanks if anyone can answer this.

Best regards,

pgsql-docs by date

Next:From: Pierce TylerDate: 2001-03-05 17:39:19
Subject: RefGuide diffs
Previous:From: Pierce TylerDate: 2001-03-05 17:09:07
Subject: Reference Guide diffs

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group