mvcc catalo gsnapshots and TopTransactionContext

Поиск
Список
Период
Сортировка
От Andres Freund
Тема mvcc catalo gsnapshots and TopTransactionContext
Дата
Msg-id 20130711082855.GF27898@alap2.anarazel.de
обсуждение исходный текст
Ответы Re: mvcc catalo gsnapshots and TopTransactionContext
Re: mvcc catalo gsnapshots and TopTransactionContext
Список pgsql-hackers
Hi,

since the mvcc catalog patch has gone in we require all users of
systable_* to be in a valid transaction since the snapshot is copied via
CopySnapshot() in RegisterSnapshot(). Which we call in
systable_beginscan(). CopySnapshot() allocates the copied snapshot in
TopTransactionContext.

There doesn't seem be an explicitly stated rule that we cannot use the
syscaches outside of a transaction - but effectively that's required
atm.

Not having investigated at all so far I am not sure how much in core
code that breaks, but it certainly broke some out of tree code of mine
(bidirectional replication stuff, bdr branch on git.pg.o).

Is that acceptable?

Greetings,

Andres Freund

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



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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: Support for REINDEX CONCURRENTLY
Следующее
От: Dean Rasheed
Дата:
Сообщение: Re: how to find out whether a view is updatable