| From: | Dan Ports <drkp(at)csail(dot)mit(dot)edu> |
|---|---|
| To: | YAMAMOTO Takashi <yamt(at)mwd(dot)biglobe(dot)ne(dot)jp> |
| Cc: | Kevin(dot)Grittner(at)wicourts(dot)gov, heikki(dot)linnakangas(at)enterprisedb(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SSI bug? |
| Date: | 2011-02-22 02:41:29 |
| Message-ID: | 20110222024129.GC74913@csail.mit.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Feb 21, 2011 at 11:42:36PM +0000, YAMAMOTO Takashi wrote:
> i tested ede45e90dd1992bfd3e1e61ce87bad494b81f54d + ssi-multi-update-1.patch
> with my application and got the following assertion failure.
>
> #4 0x0827977e in CheckTargetForConflictsIn (targettag=0xbfbfce78)
> at predicate.c:3657
> 3657 Assert(locallock != NULL);
It looks like CheckTargetForConflictsIn is making the assumption that
the backend-local lock table is accurate, which was probably even true
at the time it was written. Unfortunately, it hasn't been for a while,
and the new changes for tuple versions make it more likely that this
will actually come up.
The solution is only slightly more complicated than just removing the
assertion. Unless Kevin beats me to it, I'll put together a patch later
tonight or tomorrow. (I'm at the airport right now.)
Dan
--
Dan R. K. Ports MIT CSAIL http://drkp.net/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Itagaki Takahiro | 2011-02-22 03:08:31 | UNLOGGED tables in psql \d |
| Previous Message | Andrew Dunstan | 2011-02-22 02:38:02 | Re: configure gaps |