Re: Query running for 12 hours

Поиск
Список
Период
Сортировка
От Adrian Klaver
Тема Re: Query running for 12 hours
Дата
Msg-id 7c2c3680-49a7-e6ce-82e1-171ba3e6db43@aklaver.com
обсуждение исходный текст
Ответ на Re: Query running for 12 hours  (Yavuz Selim Sertoğlu <yavuzselim.sertoglu@bisoft.com.tr>)
Ответы Re: Query running for 12 hours  (Yavuz Selim Sertoğlu <yavuzselim.sertoglu@bisoft.com.tr>)
Список pgsql-general
On 05/30/2018 06:54 AM, Yavuz Selim Sertoğlu wrote:
> I am just a regular dba so I dont know what's sent from application 
> exactly but I assume now()-1 week.
> In the log file, there are two more same queries. And their value is 
> *2018-05-23 02:00:00*
> 

And these queries are not showing up in pg_stat_activity as still active?

> *
> *I explain analyzed same query with that value and its completed in 6 
> seconds.*
>
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> ---------------------------------------------------------------------------------------------------------------
>   Hash Left Join  (cost=388.90..60022.26 rows=1165585 width=503) (actual 
> time=34.951..4338.432 rows=1167885 loops=1)
>     Output: this_.id, this_.islemturu, this_.kullanici_id, 
> this_.loglananislem, this_.oncekiveri, this_.tarih, this_.veri, 
> kullanici2_.id, kullanici2_.ad, kullanici2_.aktif, kullanici2_.dbuser, kull
> anici2_.eposta, kullanici2_.kullaniciadi, kullanici2_.kullanicitipienum, 
> kullanici2_.parola, kullanici2_.soyad
>     Hash Cond: (this_.kullanici_id = kullanici2_.id)
>     Buffers: shared hit=29227
>     ->  Seq Scan on public.t_log_kaydi this_  (cost=0.00..43626.00 
> rows=1165585 width=374) (actual time=0.010..1611.388 rows=1167885 loops=1)
>           Output: this_.id, this_.islemturu, this_.loglananislem, 
> this_.oncekiveri, this_.tarih, this_.veri, this_.kullanici_id
>           Filter: (this_.tarih < '2018-05-23 02:00:00.023'::timestamp 
> without time zone)
>           Rows Removed by Filter: 3178
>           Buffers: shared hit=29034
>     ->  Hash  (cost=278.40..278.40 rows=8840 width=129) (actual 
> time=34.770..34.770 rows=9134 loops=1)
>           Output: kullanici2_.id, kullanici2_.ad, kullanici2_.aktif, 
> kullanici2_.dbuser, kullanici2_.eposta, kullanici2_.kullaniciadi, 
> kullanici2_.kullanicitipienum, kullanici2_.parola, kullanici2_.
> soyad
>           Buckets: 16384  Batches: 1  Memory Usage: 1604kB
>           Buffers: shared hit=190
>           ->  Seq Scan on public.t_kullanici kullanici2_  
> (cost=0.00..278.40 rows=8840 width=129) (actual time=0.005..16.630 
> rows=9134 loops=1)
>                 Output: kullanici2_.id, kullanici2_.ad, 
> kullanici2_.aktif, kullanici2_.dbuser, kullanici2_.eposta, 
> kullanici2_.kullaniciadi, kullanici2_.kullanicitipienum, 
> kullanici2_.parola, kullan
> ici2_.soyad
>                 Buffers: shared hit=190
> * Planning time: 2.331 ms*
> * Execution time: 5431.817 ms*
> *
> *
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com


В списке pgsql-general по дате отправления:

Предыдущее
От: Melvin Davidson
Дата:
Сообщение: Re: Query running for 12 hours
Следующее
От: Adrian Klaver
Дата:
Сообщение: Re: Query running for 12 hours