Re: Allow "snapshot too old" error, to prevent bloat

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Allow "snapshot too old" error, to prevent bloat
Дата
Msg-id CA+TgmoaG4CVXp7nbsVqm16ZvVFw5au9L2QvOQjRcrd7Fm10XvA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Allow "snapshot too old" error, to prevent bloat  (Rui DeSousa <rui@crazybean.net>)
Ответы Re: Allow "snapshot too old" error, to prevent bloat  (Andrew Dunstan <andrew@dunslane.net>)
Список pgsql-hackers
On Sun, Mar 15, 2015 at 8:04 PM, Rui DeSousa <rui@crazybean.net> wrote:
> Would a parameter to auto terminate long running transactions be a better solution? Terminating the long running
transactionwould allow for the normal vacuuming process to cleanup the deleted records thus avoiding database bloat
withoutintroducing new semantics to Postgres's MVCC. I would also recommend that the default be disabled. 

An advantage of Kevin's approach is that you don't have to abort *all*
long-running transactions, only those that touch data which has been
modified since then.  If your system is read-mostly, that could
dramatically reduce the number of aborts.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



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

Предыдущее
От: Stephen Frost
Дата:
Сообщение: Re: get_object_address support for additional object types
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: get_object_address support for additional object types