RE: scans on table fail to be excluded by partition bounds - Mailing list pgsql-performance

From Steven Winfield
Subject RE: scans on table fail to be excluded by partition bounds
Date
Msg-id E9FA92C2921F31408041863B74EE4C2001BD7B6764@CCPMAILDAG03.cantab.local
Whole thread Raw
In response to scans on table fail to be excluded by partition bounds  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: scans on table fail to be excluded by partition bounds
List pgsql-performance
> ts=# explain SELECT * FROM eric_enodeb_cell_metrics WHERE start_time
> BETWEEN '2019-01-01 04:00' AND '2019-01-01 05:00' OR start_time BETWEEN
> '2019-01-02 04:00' AND '2019-01-02 05:00'

Maybe it's because of the implicit usage of the local timezone when the strings are cast to (timestamp with time zone)
inthe values you give for start_time here? 
What happens if you specify it using "TIMESTAMP WITH TIME ZONE '2019-01-01 04:00-05'", etc.?

Steve.




pgsql-performance by date:

Previous
From: Justin Pryzby
Date:
Subject: scans on table fail to be excluded by partition bounds
Next
From: Rick Otten
Date:
Subject: Re: materialized view refresh of a foreign table