Re: tuptoaster.c must *not* use SnapshotAny - Mailing list pgsql-hackers

From Hiroshi Inoue
Subject Re: tuptoaster.c must *not* use SnapshotAny
Date
Msg-id 3C47880B.1D8B4D64@tpf.co.jp
Whole thread Raw
In response to Re: tuptoaster.c must *not* use SnapshotAny  (Jan Wieck <janwieck@yahoo.com>)
Responses Re: tuptoaster.c must *not* use SnapshotAny  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> 
> Hiroshi Inoue <Inoue@tpf.co.jp> writes:
> > SnapshotToast doesn't seem a proper solution to me
> 
> Do you have a better idea in mind?

The same snapshot for both the main and the toast table
seems better though I don't know how it's difficult to
change. For example is it possible to update a toast
chunk partially using SnapshotToast ?

regards,
Hiroshi Inoue


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug in pg_dump/restore -o
Next
From: Tom Lane
Date:
Subject: Re: tuptoaster.c must *not* use SnapshotAny