Re: [PERFORM] printing results of query to file in different times

Geez ... I just saw how my last message got mangled. Trying again. On 9/5/2017 7:28 AM, Mariel Cherkassky wrote: I didn't understand what do you mean by REPEATABLE_READ. I was referring to transaction isolation levels.  When multiple transactions are running concurrently, the DBMS can (or n

Re: [PERFORM] printing results of query to file in different times

Hi Mariel, Please don't top post in the Postgresql groups. On 9/5/2017 7:28 AM, Mariel Cherkassky wrote: 2017-08-31 16:24 GMT+03:00 George Neuner >: > >> One thing you might look at is the isolation level of the query. >> If you are using READ_COMMITTED or less, a

Re: [PERFORM] slow index scan performance

Trying on another server, it gives different result. -> Index Scan using response_log_by_activity on public.response_log rl2 (cost=0.00..50.29 rows=17 width=8) (actual time=0.955..0.967 rows=0 loops=30895) Output: rl2.activity_id, rl2.feed_id

Re: [PERFORM] slow index scan performance

It's Postgres 9.1.24 on RHEL 6.5 On Tue, Sep 5, 2017 at 8:24 PM, Soni M wrote: > Consider these 2 index scan produced by a query > > -> Index Scan using response_log_by_activity on public.response_log rl2 > (cost=0.00..51.53 rows=21 width=8) (actual time=9.017..9.056 rows=0 > loops=34098) >

[PERFORM] slow index scan performance

Consider these 2 index scan produced by a query -> Index Scan using response_log_by_activity on public.response_log rl2 (cost=0.00..51.53 rows=21 width=8) (actual time=9.017..9.056 rows=0 loops=34098) Output: rl2.activity_id, rl2.feed_id

Re: [PERFORM] printing results of query to file in different times

I'm using an extension that is called orafce. Yes I add the raise notice in order to see what happening but it doesnt work faster. The execution plan isnt relevant because It happens for many queries not for a specific one. I didnt understand what do you mean by REPEATABLE_READ . 2017-08-31 16:24