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

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Steven Winfield <Steven(dot)Winfield(at)cantabcapital(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: scans on table fail to be excluded by partition bounds
Date: 2019-06-26 18:03:20
Message-ID: 20190626180320.GA28953@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Hugh Ranalli 2019-06-26 18:06:38 Re: Perplexing, regular decline in performance
Previous Message Igor Neyman 2019-06-26 14:29:14 RE: Max_connections limit