| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-general(at)postgresql(dot)org, Dan Armbrust <daniel(dot)armbrust(dot)list(at)gmail(dot)com> |
| Subject: | Re: recover corrupt DB? |
| Date: | 2009-05-02 02:50:09 |
| Message-ID: | 49FBB4E1.40903@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane wrote:
> Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
>> I've been wondering about this for a while. Why does Pg end up with the
>> database in an unusable, unrecoverable state after a disk-full error?
>
> It doesn't. There must have been some other filesystem misfeasance
> involved in the OP's problem.
Cool - so it's definitely meant to handle disk-full fine. That's what I
was concerned about.
These reports seem to come up a bit, with disk full issues resulting in
the need to pg_resetxlog, dump, and re-initdb, but I wouldn't be too
shocked if they all turned out to be on xfs or something like that.
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2009-05-02 03:18:42 | Re: Possible to prevent transaction abort? |
| Previous Message | rwade | 2009-05-02 01:54:59 | function in pgAdmin |