Re: Help me recovering data

From: pgsql(at)mohawksoft(dot)com
To: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Kouber Saparev" <postgresql(at)saparev(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Help me recovering data
Date: 2005-02-16 14:39:09
Message-ID: 16703.24.91.171.78.1108564749.squirrel@mail.mohawksoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> The checkpointer is entirely incapable of either detecting the problem
>> (it doesn't have enough infrastructure to examine pg_database in a
>> reasonable way) or preventing backends from doing anything if it did
>> know there was a problem.
>
> Well, I guess I meant 'some regularly running process'...
>
>>>I think people'd rather their db just stopped accepting new transactions
>>>rather than just losing data...
>>
>> Not being able to issue new transactions *is* data loss --- how are you
>> going to get the system out of that state?
>
> Not allowing any transactions except a vacuum...
>
>> autovacuum is the correct long-term solution to this, not some kind of
>> automatic hara-kiri.
>
> Yeah, seems like it should really happen soon...
>
> Chris

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Eliot Simcoe 2005-02-16 15:22:39 Work on Table Inheritance
Previous Message Merlin Moncure 2005-02-16 13:42:12 Re: