Re: Planner performance extremely affected by an hanging transaction (20-30 times)?

Поиск
Список
Период
Сортировка
От didier
Тема Re: Planner performance extremely affected by an hanging transaction (20-30 times)?
Дата
Msg-id CAJRYxuJkgePh2AntoaMCsrHQ+mdaGxw6puOVCnmOJaAyp_viyg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Planner performance extremely affected by an hanging transaction (20-30 times)?  (jesper@krogh.cc)
Ответы Re: Planner performance extremely affected by an hanging transaction (20-30 times)?
Список pgsql-performance
Дерево обсуждения
Hi


On Tue, Sep 24, 2013 at 5:01 PM, <jesper@krogh.cc> wrote:

Apparently it is waiting for locks, cant the check be make in a
"non-blocking" way, so if it ends up waiting for a lock then it just
assumes non-visible and moves onto the next non-blocking?

Not only, it's a reason but you can get the same slow down with only  one client and a bigger insert.

The issue is that a btree search for one value  degenerate to a linear search other  1000 or more tuples.

As a matter of fact you get the same slow down after a rollback until autovacuum, and if autovacuum can't keep up...

Didier

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

Предыдущее
От: Josh Berkus
Дата:
Сообщение: Re: Planner performance extremely affected by an hanging transaction (20-30 times)?
Следующее
От: François Deliège
Дата:
Сообщение: Bringing up new slaves faster