| From: | "Robert Creager" <pgsql-bugs(at)logicalchaos(dot)org> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: heap_mark4update: (am)invalid tid |
| Date: | 2003-04-12 14:30:11 |
| Message-ID: | 3E97CE93.17836.856F14D@localhost |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> "Robert Creager" <pgsql-bugs(at)logicalchaos(dot)org> writes:
> > I found reference to this problem at
> > http://archives.postgresql.org/pgsql-general/2003-02/msg00135.php,
> > but there was no apparent resolution.
>
> If (a) obs_v_trigger is a BEFORE trigger, *and* (b) the problem UPDATE
> could try to update a row of obs_v more than once (ie, there are
> multiple rows in obs_i/files that match a row in obs_v), then I think
> this is a known problem. Otherwise, we need to dig more ...
>
> regards, tom lane
Yes, and yes. Any work arounds (ie current sources, smarter SQL),
other than to break this up into multiple updates?
Thanks,
Rob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-04-12 16:45:17 | Re: heap_mark4update: (am)invalid tid |
| Previous Message | Ennio-Sr | 2003-04-12 14:12:10 | Re: Psql 'Expanded display (\x)' behaviour |