Re: Vacuum threshold and non-serializable read-only transaction

Поиск
Список
Период
Сортировка
От ITAGAKI Takahiro
Тема Re: Vacuum threshold and non-serializable read-only transaction
Дата
Msg-id 20080128153720.7D68.52131E4D@oss.ntt.co.jp
обсуждение исходный текст
Ответ на Re: Vacuum threshold and non-serializable read-only transaction  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Surely this'd require having those transactions display exactly what
> their current oldest-xmin is.  We've talked about that before, and it
> seems a good idea, but it requires a bit more infrastructure than is
> there now --- we'd need some snapshot-management code that could keep
> track of all live snapshots within each backend.

I see. I'll need to avoid long transactions during heavily updates.
The additonal management seems to be good, but not so easy
because we should not lead lock contentions at the same time.

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center




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

Предыдущее
От: Neil Conway
Дата:
Сообщение: RFC: array_agg() per SQL:200n
Следующее
От: "Premsun Choltanwanich"
Дата:
Сообщение: Slow Query problem