Re: Read Uncommitted

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: Read Uncommitted
Дата
Msg-id 483B1E9A.9020506@enterprisedb.com
обсуждение исходный текст
Ответ на Re: Read Uncommitted  (Simon Riggs <simon@2ndquadrant.com>)
Список pgsql-hackers
Simon Riggs wrote:
> On Mon, 2008-05-26 at 13:25 -0400, Tom Lane wrote:
>> Hannu Krosing <hannu@krosing.net> writes:
>>> On Mon, 2008-05-26 at 16:55 +0200, Peter Eisentraut wrote:
>>>> If the data in a table never changes, why would VACUUM or HOT need to touch 
>>>> it?  The use case isn't clear to me.
>>> I guess the use-case is about a long read-write transaction doing
>>> read-only access to an update-only table and thus blocking vacuum on
>>> other tables.
>> ... in which case the proposed kluge would result in unstable,
>> unpredictable answers, so there is still no plausible use-case.
> 
> Separate databases?

OldestXmin calculation only includes transactions in the same database, 
except when vacuuming shared relations.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: keyword list/ecpg
Следующее
От: Simon Riggs
Дата:
Сообщение: Re: Read Uncommitted