Christopher Kings-Lynne wrote:
>> The mistake has only come up two or three times that I can remember,
>> which doesn't elevate it to the category of stuff that I want to install
>> a lot of mechanism to prevent. Especially not mechanism that would get
>> in the way of reasonable uses. I think it's sufficient to have a
>> recovery procedure.
> Hmmm - I agree it's difficult, but somehow I think it's something we
> should do. Just imagine if some major user of postgres did it -
> they'd be screaming blue murder...
IMHO we (that is Christopher, me and others maintaining easy to (mis)use
tools) should warn the users about what they're going to do.
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2004-05-25 01:35:53|
|Subject: Re: New horology failure |
|Previous:||From: Gaetano Mendola||Date: 2004-05-24 21:47:17|
|Subject: Re: Optimizer bug??|