| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql(at)mohawksoft(dot)com |
| Cc: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "Kouber Saparev" <postgresql(at)saparev(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Help me recovering data |
| Date: | 2005-02-16 15:31:05 |
| Message-ID: | 24159.1108567865@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
pgsql(at)mohawksoft(dot)com writes:
> Maybe I'm missing something, but shouldn't the prospect of data loss (even
> in the presense of admin ignorance) be something that should be
> unacceptable? Certainly within the realm "normal PostgreSQL" operation.
[ shrug... ] The DBA will always be able to find a way to shoot himself
in the foot. We've seen several instances of people blowing away
pg_xlog and pg_clog, for example, because they "don't need log files".
Or how about failing to keep adequate backups? That's a sure way for an
ignorant admin to lose data too.
Once autovacuum gets to the point where it's used by default, this
particular failure mode should be a thing of the past, but in the
meantime I'm not going to panic about it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgsql | 2005-02-16 16:08:29 | Re: Help me recovering data |
| Previous Message | Eliot Simcoe | 2005-02-16 15:22:39 | Work on Table Inheritance |