| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | 郭 勇 <guoyongxhzhf(at)icloud(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: postgresql infinite loop |
| Date: | 2016-09-29 13:25:59 |
| Message-ID: | 6035.1475155559@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?GB2312?B?ufkg08I=?= <guoyongxhzhf(at)icloud(dot)com> writes:
> I have a postgresql infinite problem.
> when inserting data, a postgresql process involve to infinite loop and cpu usage is 100%. perf top show that LWacquirelock is most costful.
> Callstack is below.
Given that stack trace, I'd have to guess that this is caused by a
circular chain of right-links in a btree index. How it got that
way is hard to say, but reindexing the index ought to fix it.
If you can show a recipe for producing an index that's broken
this way from a standing start, we'd be very interested.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-09-29 13:47:09 | Re: Speed up Clog Access by increasing CLOG buffers |
| Previous Message | 郭 勇 | 2016-09-29 13:12:59 | postgresql infinite loop |