Re: Eliminating PD_ALL_VISIBLE, take 2

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Robins <robins(at)pobox(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Eliminating PD_ALL_VISIBLE, take 2
Date: 2013-07-02 00:59:24
Message-ID: CA+Tgmob-zYrqBOPDy1+_SSwu9=h_eUdanPHH1vomCYCfus7W9g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 1, 2013 at 8:23 PM, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> 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".)

One of several relevant emails is at:

http://www.postgresql.org/message-id/51A7473C.6070208@vmware.com

It is definitely possible that I am mixing up two different things.
But if I am, I don't know what the other one is.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2013-07-02 02:39:46 Re: Eliminating PD_ALL_VISIBLE, take 2
Previous Message Craig Ringer 2013-07-02 00:32:30 Re: Support for RANGE ... PRECEDING windows in OVER