Re: Should we remove "not fast" promotion at all? - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Should we remove "not fast" promotion at all?
Date
Msg-id 20130806024043.GA31572@alap2.anarazel.de
Whole thread Raw
In response to Should we remove "not fast" promotion at all?  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Should we remove "not fast" promotion at all?  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
Hi,

On 2013-08-06 03:24:58 +0900, Fujii Masao wrote:
> Hi all,
> 
> We discussed the $SUBJECT in the following threads:
> http://www.postgresql.org/message-id/CA+TgmoZbR+WL8E7MF_KRp6fY4FD2pMr11TPiuyjMFX_Vtg1Wrw@mail.gmail.com
> http://www.postgresql.org/message-id/CAHGQGwEBUvgcx8X+Z0Hh+VdwYcJ8KCuRuLt1jSsxeLxPcX=0_w@mail.gmail.com
> 
> Our consensus seems to remove "not fast" promotion at all
> because there is no use case for that promotion.
> 
> Attached patch removes "not fast" promotion. Barring any objections,
> I will commit this patch.

FWIW I'd rather keep plain promotion for a release or two. TBH, I have a
bit of trust issues regarding the new method, and I'd like to be able to
test potential issues against a stock postgres by doing a normal instead
of a fast promotion.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Should we remove "not fast" promotion at all?
Next
From: Andres Freund
Date:
Subject: Re: HeapTupleSatisfiesDirty fails to test HEAP_XMAX_IS_LOCKED_ONLY for TransactionIdIsInProgress(...)