From: | Cedric Leong <cedricleong(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Re: Date vs Timestamp without timezone Partition Key |
Date: | 2020-06-06 02:12:26 |
Message-ID: | CAD6i=X1RWpg1GR0-h-KO0n=WE6PKoWeUs-pytgX6sfZSczQ54w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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 <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Cedric Leong <cedricleong(at)gmail(dot)com> 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 comparisons vs 64-bit integer
> comparisons.
>
> On a 32-bit machine it's possible that an index on a date column
> will be physically smaller, so you could get some wins from reduced
> I/O. But on (most?) 64-bit machines that difference goes away too,
> because of alignment restrictions.
>
> As always, YMMV; it never hurts to do your own testing.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2020-06-06 02:16:50 | Re: Date vs Timestamp without timezone Partition Key |
Previous Message | Jeff Janes | 2020-06-05 13:51:29 | Re: When to use PARTITION BY HASH? |