I can confirm that was the issue, after removing the expression and using
only what was indexed it definitely fixed the query plan. I appreciate all
the help you've given me, I didn't really think to look there but it makes
a ton of sense that a filter on the database would only work well if it's
i
On Sat, 6 Jun 2020 at 14:49, Cedric Leong wrote:
> It's less of a complaint rather than just a warning not to do what I did.
My point was really that nobody really knew what you did or what you
did it on. So it didn't seem like a worthwhile warning as it
completely lacked detail.
> These tests a
It's less of a complaint rather than just a warning not to do what I did.
Version:
PostgreSQL 11.6 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.9.3, 64-bit
The actual command list would probably be impractical to put in here just
because the majority of it would just be creating a large amount
On Sat, 6 Jun 2020 at 14:12, Cedric Leong wrote:
> Somewhat unrelated but note to anyone who wants to swap out partition keys.
> Don't create a clone of the table with the new partition key and insert data.
> It messes up the query planner massively and makes everything much slower.
That compla
Somewhat unrelated but note to anyone who wants to swap out partition keys.
Don't create a clone of the table with the new partition key and insert
data. It messes up the query planner massively and makes everything much
slower.
On Mon, May 25, 2020 at 12:48 AM Tom Lane wrote:
> Cedric Leong wr
Cedric Leong writes:
> Just in case someone is interested enough to answer this. Does anyone know
> if the performance for a date column vs a timestamp column as a partition
> key is large?
I doubt it's even measurable, at least on 64-bit machines. You're
basically talking about 32-bit integer c
Just in case someone is interested enough to answer this. Does anyone know
if the performance for a date column vs a timestamp column as a partition
key is large? What i mean with large is that say you have 6 partitions with
10GB each. Would it be a 10 second+ difference? An explanation of how this
