Re: Eliminating PD_ALL_VISIBLE, take 2

Поиск
Список
Период
Сортировка
От Jeff Davis
Тема Re: Eliminating PD_ALL_VISIBLE, take 2
Дата
Msg-id 1372724606.6398.5.camel@sussancws0025
обсуждение исходный текст
Ответ на Re: Eliminating PD_ALL_VISIBLE, take 2  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: Eliminating PD_ALL_VISIBLE, take 2  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
On Mon, 2013-07-01 at 16:05 -0400, Robert Haas wrote:
> The other concern I remember being expressed (and not just by me, but
> by a number of people) is that your patch turns loss of a visibility
> map bit into a data corruption scenario, which it currently isn't.
> Right now, if your visibility map gets corrupted, you can always
> recover by deleting it.  Under your proposal that would no longer be
> possible.  I think that's sufficient grounds to reject the patch by
> itself, even if there were no other issues.  If that doesn't strike
> you as very dangerous, I'm baffled as to why not.

Can you point me to that criticism? Why can't you just drop the VM
completely if it becomes corrupted?

(You might be referring to another idea of mine that was related to
Andres's proposal for "getting rid of freezing".)

Regards,Jeff Davis





В списке pgsql-hackers по дате отправления:

Предыдущее
От: Josh Kupershmidt
Дата:
Сообщение: Re: fixing pg_ctl with relative paths
Следующее
От: Craig Ringer
Дата:
Сообщение: Re: Support for RANGE ... PRECEDING windows in OVER