Re: SSI bug?

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "YAMAMOTO Takashi" <yamt(at)mwd(dot)biglobe(dot)ne(dot)jp>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SSI bug?
Date: 2011-02-14 19:04:41
Message-ID: 4D592869020000250003A99A@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

YAMAMOTO Takashi <yamt(at)mwd(dot)biglobe(dot)ne(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2011-02-14 19:07:17 Re: sepgsql contrib module
Previous Message Alvaro Herrera 2011-02-14 19:01:36 Re: sepgsql contrib module