From: Justin Pryzby <pryzby@telsasoft.com>
To: Steven Winfield <Steven.Winfield@cantabcapital.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: scans on table fail to be excluded by partition bounds
Date: Wed, 26 Jun 2019 13:03:20 -0500
Message-ID: <20190626180320.GA28953@telsasoft.com> (raw)
In-Reply-To: <E9FA92C2921F31408041863B74EE4C2001BD7B6764@CCPMAILDAG03.cantab.local>
References: <20190624173146.GA32632@telsasoft.com>
<E9FA92C2921F31408041863B74EE4C2001BD7B6764@CCPMAILDAG03.cantab.local>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pryzby@telsasoft.com, Steven.Winfield@cantabcapital.com
Subject: Re: scans on table fail to be excluded by partition bounds
In-Reply-To: <20190626180320.GA28953@telsasoft.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox