Re: Vacuum threshold and non-serializable read-only transaction - Mailing list pgsql-hackers

From ITAGAKI Takahiro
Subject Re: Vacuum threshold and non-serializable read-only transaction
Date
Msg-id 20080128153720.7D68.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to Re: Vacuum threshold and non-serializable read-only transaction  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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 by date:

Previous
From: Neil Conway
Date:
Subject: RFC: array_agg() per SQL:200n
Next
From: "Premsun Choltanwanich"
Date:
Subject: Slow Query problem