Re: One tuple per transaction

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: One tuple per transaction
Дата
Msg-id 2284.1110948270@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: One tuple per transaction  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
Список pgsql-performance
Alvaro Herrera <alvherre@dcc.uchile.cl> writes:
> On Tue, Mar 15, 2005 at 06:51:19PM -0500, Tom Lane wrote:
>> I believe VACUUM already knows that xmin = xmax implies the tuple
>> is dead to everyone.

> Huh, that is too simplistic in a subtransactions' world, isn't it?

Well, it's still correct as a fast-path check.  There are extensions
you could imagine making ... but offhand I agree that it's not worth
the trouble.  Maybe in a few years when everyone and his sister is
using subtransactions constantly, we'll feel a need to optimize these
cases.

            regards, tom lane

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

Предыдущее
От: "Greg Sabino Mullane"
Дата:
Сообщение: Re: Changing the random_page_cost default (was: cpu_tuple_cost)
Следующее
От: Greg Stark
Дата:
Сообщение: Re: cpu_tuple_cost