Re: [GENERAL] Matching indexe for timestamp

2017-01-09 Thread Vitaly Burovoy
On 1/9/17, Job wrote: > Hello, > > on this table: > > Table "public.gruorari_tmp" > Column | Type | > Modifiers > ---++-- > id

Re: [GENERAL] Matching indexe for timestamp

2017-01-09 Thread David G. Johnston
On Mon, Jan 9, 2017 at 2:58 PM, Job wrote: > > But in the query planner, at that point, Postgresql 9.6.1 seems not to use > any index (single on dalle / alle field and combindex index on dalle+alle) > but it use seqscan: > > Seq Scan on gruorari_tmp (cost=0.00..5.90 rows=290 width=68) (actual >

Re: R: [GENERAL] Matching indexe for timestamp

2017-01-09 Thread Adrian Klaver
On 01/09/2017 03:38 PM, Job wrote: Please also reply to list. I do not have time at the moment to go through this, someone else on the list might. Hi Adrian, You are right; here is the query and the planner. I think indexes are not used at all! /F EXPLAIN ANALYZE select webrecord.do

Re: [GENERAL] Matching indexe for timestamp

2017-01-09 Thread Adrian Klaver
On 01/09/2017 01:58 PM, Job wrote: Hello, on this table: Table "public.gruorari_tmp" Column | Type | Modifiers ---++-- id

[GENERAL] Matching indexe for timestamp

2017-01-09 Thread Job
Hello, on this table: Table "public.gruorari_tmp" Column | Type |Modifiers ---++-- id| n