| From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Wieck <janwieck(at)yahoo(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: tuptoaster.c must *not* use SnapshotAny |
| Date: | 2002-01-18 01:55:44 |
| Message-ID: | 3C4780A0.F4C3022C@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
>
> 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.
AFAIR SnapshotAny was introduced for Foreign Key stuff.
SnapshotToast doesn't seem a proper solution to me but
7.2 should be released ASAP anyway.
regards,
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-01-18 02:05:15 | Re: Bug in pg_dump/restore -o |
| Previous Message | Stephan Szabo | 2002-01-18 01:20:59 | Re: UPDATE Query problem |