> 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
>Has anyone been through this type of problem?
>
You could set up a new, empty db (with checksums enabled, etc.) on the new
hardware and then use logical replication to sync across all the data from the
existing cluster.
(This logical replica could be doing binary replication to hot standbys
Thanks, everyone, for your comments.
I guess if something looks too good to be true then it usually is!
Steven.
(P.S. Apologies for the email disclaimer - it is added by our mail server, not
my mail client, and its exclusion list is on the fritz)
Hi,
(Apologies if this isn't the right place to post this)
A few days ago a blog post appeared on phoronix.com[1] comparing GCC 8.3.0
against 9.0.1 on Intel cascadelake processors.
A notable difference was seen in the PostgreSQL benchmark (v10.3, pgbench,
read/write, more detail below), both
Do you have constraint_exclusion set correctly (i.e. ‘on’ or ‘partition’)?
If so, does the EXPLAIN output mention all of your parent partitions, or are
some being successfully pruned?
Planning times can be sped up significantly if the planner can exclude parent
partitions, without ever having to
