Re: Read Uncommitted - Mailing list pgsql-hackers

From ITAGAKI Takahiro
Subject Re: Read Uncommitted
Date
Msg-id 20080526195344.C96A.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to Re: Read Uncommitted  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Read Uncommitted  ("Koichi Suzuki" <koichi.szk@gmail.com>)
Re: Read Uncommitted  (Simon Riggs <simon@2ndquadrant.com>)
List 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 by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Proposal: temporal extension "period" data type
Next
From: "Koichi Suzuki"
Date:
Subject: Re: Read Uncommitted