Re: SSI bug? - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: SSI bug?
Date
Msg-id 4D592869020000250003A99A@gw.wicourts.gov
Whole thread Raw
In response to Re: SSI bug?  (yamt@mwd.biglobe.ne.jp (YAMAMOTO Takashi))
Responses Re: SSI bug?  (yamt@mwd.biglobe.ne.jp (YAMAMOTO Takashi))
List pgsql-hackers
YAMAMOTO Takashi <yamt@mwd.biglobe.ne.jp> wrote:
>> Did you notice whether the loop involved multiple tuples within a
>> single page?
> 
> if i understand correctly, yes.
> 
> the following is a snippet of my debug code (dump targets when
> triggerCheckTargetForConflictsIn loops >1000 times) and its
> output.the same locktag_field3 value means the same page, right?
Right.
> the table seems mostly hot-updated, if it matters.
> idx_scan          | 53681
> idx_tup_fetch     | 52253
> n_tup_ins         | 569
> n_tup_upd         | 12054
> n_tup_del         | 476
> n_tup_hot_upd     | 12041
> n_live_tup        | 93
> n_dead_tup        | 559
That probably matters a lot.
> analyze_count     | 4922528128875102208
> autoanalyze_count | 7598807461784802080
> 
> (values in the last two columns seems bogus.
> i don't know if it's related or not.)
That seems unlikely to be related to this problem.  It sure does
look odd, though.  Maybe post that in a separate thread?
Thanks for all the additional info.  I'll keep digging.
-Kevin


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: sepgsql contrib module
Next
From: Andrew Dunstan
Date:
Subject: Re: sepgsql contrib module