Re: brin index vacuum versus transaction snapshots

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: brin index vacuum versus transaction snapshots
Дата
Msg-id CANP8+jK8uJSHe4j7tjuQRQsthUawUx+-JMnoFnzXzCovRiA9fQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: brin index vacuum versus transaction snapshots  (Kevin Grittner <kgrittn@ymail.com>)
Список pgsql-hackers
Дерево обсуждения
On 31 July 2015 at 15:48, Kevin Grittner <kgrittn@ymail.com> wrote:

Reread the thread. 

I stand corrected.
 
The error is being hit on a VACUUM command
(which is not, of course in any explicit transaction).

Seems like VACUUM only ever needs a read-committed snapshot. Whether it takes a read-committed or repeatable read makes no difference.

Does brin_summarize_new_values() need to track what it reads for serializable transactions?

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

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

Предыдущее
От: Kevin Grittner
Дата:
Сообщение: Re: brin index vacuum versus transaction snapshots
Следующее
От: Jesper Pedersen
Дата:
Сообщение: RequestAddinLWLocks(int n)