Re: Read Uncommitted
| От | ITAGAKI Takahiro |
|---|---|
| Тема | Re: Read Uncommitted |
| Дата | |
| Msg-id | 20080526195344.C96A.52131E4D@oss.ntt.co.jp обсуждение исходный текст |
| Ответ на | Re: Read Uncommitted (Simon Riggs <simon@2ndquadrant.com>) |
| Ответы |
Re: Read Uncommitted
Re: Read Uncommitted |
| Список | pgsql-hackers |
Simon Riggs <simon@2ndquadrant.com> wrote:
> The use of this is clear though: allowing long running transactions
> against unchanging data to not interfere with other activities. It will
> also have importance in a Hot Standby mode.
I have an use of the dirty read -- pg_start_backup().
In 8.3, pg_start_backup takes long time, that is typically
{ checkpoint_timeout * checkpoint_completion_target }.
If we have some updating transaction during pg_start_backup,
updated tables cannot be vacuumed well. READ UNCOMMITTED mode
could help us in such a situation.
BEGIN; SET TRANSACTION READ UNCOMMITTED; SELECT pg_start_backup(timeofday()); END;
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: