| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Re: Re: [GENERAL] 回复: postgres cpu 100% need help |
| Date: | 2015-10-28 08:28:50 |
| Message-ID: | 56308742.5070708@hogranch.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 10/28/2015 12:12 AM, 657985552(at)qq(dot)com wrote:
> Thank you for your reply.
> tshow=> explain (analyze, buffers) select count(t.*) from tshow.res_room_weight t,tshow.res_room_info r
>
> tshow-> where t.subcatlg_id=46
> tshow-> and t.roomid = r.actorid
> tshow-> and r.levels>=0;
http://explain.depesz.com/s/oKN5
shows where the time is spent in that query, but as you say, that one
the timing was fine. there's a lot of time being spent in a seq_scan
of res_room_info.
I would have written that query as the inner join it is, but that
probably won't effect how it's executed.
select ... from tshow.res_room_weight t join tshow.res_room_info r on
(t.roomid = r.actorid) where t.subcatlg_id=46 and r.levels>=0;
--
john r pierce, recycling bits in santa cruz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 657985552@qq.com | 2015-10-28 08:53:43 | Re: Re: [GENERAL] Re: Re: [GENERAL] 回复: postgres cpu 100% need help |
| Previous Message | 657985552@qq.com | 2015-10-28 07:12:15 | Re: Re: [GENERAL] 回复: postgres cpu 100% need help |