Re: heap_mark4update: (am)invalid tid
| От | Tom Lane |
|---|---|
| Тема | Re: heap_mark4update: (am)invalid tid |
| Дата | |
| Msg-id | 18544.1050165917@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: heap_mark4update: (am)invalid tid ("Robert Creager" <pgsql-bugs@logicalchaos.org>) |
| Ответы |
Re: heap_mark4update: (am)invalid tid
|
| Список | pgsql-bugs |
"Robert Creager" <pgsql-bugs@logicalchaos.org> writes: >> 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 ... > Yes, and yes. Any work arounds (ie current sources, smarter SQL), > other than to break this up into multiple updates? The fix is in CVS. I've been pestering Marc to wrap up a snapshot tarball of REL7_3_STABLE branch tip, but he hasn't got round to it. So probably the easiest answer for you is to check out the branch from our anonymous-CVS server --- see basic instructions at http://www.ca.postgresql.org/users-lounge/docs/7.3/postgres/cvs.html but note the initial checkout command should be cvs ... co -P -r REL7_3_STABLE pgsql to get the stable branch rather than development tip. Note you will need a fairly current version of bison to build from source. regards, tom lane
В списке pgsql-bugs по дате отправления: