RE: scans on table fail to be excluded by partition bounds

From: Steven Winfield <Steven(dot)Winfield(at)cantabcapital(dot)com>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: RE: scans on table fail to be excluded by partition bounds
Date: 2019-06-25 10:48:01
Message-ID: E9FA92C2921F31408041863B74EE4C2001BD7B6764@CCPMAILDAG03.cantab.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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) 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.?

Steve.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Rick Otten 2019-06-25 11:03:31 Re: materialized view refresh of a foreign table
Previous Message Justin Pryzby 2019-06-24 17:31:46 scans on table fail to be excluded by partition bounds