Re: Summary and Plan for Hot Standby

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: Summary and Plan for Hot Standby
Дата
Msg-id 1258278232.14054.1009.camel@ebony
обсуждение исходный текст
Ответ на Re: Summary and Plan for Hot Standby  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: Summary and Plan for Hot Standby  (Magnus Hagander <magnus@hagander.net>)
Re: Summary and Plan for Hot Standby  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Список pgsql-hackers
On Sun, 2009-11-15 at 10:00 +0100, Magnus Hagander wrote:

> What does the time depend on?

We need to wait for all current transactions to complete. (i.e. any
backend that has (or could) take an xid or an AccessExclusiveLock before
it commits.). Similar-ish to the wait for a CREATE INDEX CONCURRENTLY.

The standby already performs this wait in the case where we overflow the
snapshot, so we have >64 subtransactions on *any* current transaction on
the master. The reason for that is (again) performance on master: we
choose not to WAL log new subtransactions.

There are various ways around this and I'm certain we'll come up with
something ingenious but my main point is that we don't need to wait for
this issue to be solved in order for HS to be usable.

-- Simon Riggs           www.2ndQuadrant.com



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

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: Postgres and likewise authentication
Следующее
От: Magnus Hagander
Дата:
Сообщение: Re: Summary and Plan for Hot Standby