Re: Query running for 12 hours
От | Adrian Klaver |
---|---|
Тема | Re: Query running for 12 hours |
Дата | |
Msg-id | 2b9d5e83-0acb-09b9-8bb4-c44a82579996@aklaver.com обсуждение исходный текст |
Ответ на | Re: Query running for 12 hours (Melvin Davidson <melvin6925@gmail.com>) |
Список | pgsql-general |
On 05/30/2018 07:00 AM, Melvin Davidson wrote: > > > > T*wo things: > * > *From your explain, it looks like you need an index on this_.tarih, > since it is doing a sequential scan when it should be using an index.* > * > * > *Also, your main problem is that when you have two exact same queries > executing at the same time, they will cause contention in* > *the disk, and neither one will make much progress. I am having a hard time seeing how two SELECT queries that on average take ~6 secs each can stay in contention for 12+ hours, especially with: waiting | f > * > > -- > *Melvin Davidson** > Maj. Database & Exploration Specialist** > Universe Exploration Command – UXC*** > Employment by invitation only! -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: