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

From Justin Pryzby
Subject Re: scans on table fail to be excluded by partition bounds
Date
Msg-id 20190626180320.GA28953@telsasoft.com
Whole thread Raw
In response to RE: scans on table fail to be excluded by partition bounds  (Steven Winfield <Steven.Winfield@cantabcapital.com>)
List pgsql-performance
On Tue, Jun 25, 2019 at 10:48:01AM +0000, Steven Winfield wrote:
> > 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)in the 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.?

It's the same.  The timezone in the constraints is the default timezone so the
that's correct.

Justin



pgsql-performance by date:

Previous
From: Igor Neyman
Date:
Subject: RE: Max_connections limit
Next
From: Hugh Ranalli
Date:
Subject: Re: Perplexing, regular decline in performance