Re: tuptoaster.c must *not* use SnapshotAny

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jan Wieck <janwieck(at)yahoo(dot)com>
Cc: Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: tuptoaster.c must *not* use SnapshotAny
Date: 2002-01-17 21:47:28
Message-ID: 25242.1011304048@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jan Wieck <janwieck(at)yahoo(dot)com> writes:
> Originally I added SnapshotAny only to solve the problem that
> the lookup of the toast table happens independant from the
> access to the main tuple, and that in fact the main tuple
> could have been deleted by the own transaction in between.

> Would changing SnapshotAny to honor HEAP_MOVED_* fix the
> problem? If nothing else by now uses this snapshot, it could
> be done in place.

What I've done is add an additional snapshot class SnapshotToast
that behaves that way. There are a couple other uses of SnapshotAny
that I didn't think I wanted to mess with.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Liam Stewart 2002-01-17 21:54:34 guc
Previous Message Bruce Momjian 2002-01-17 18:38:32 Re: Bug in pg_dump/restore -o