| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Cedric Leong <cedricleong(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Date vs Timestamp without timezone Partition Key |
| Date: | 2020-06-06 02:16:50 |
| Message-ID: | CAApHDvoidFo7EeFb8XPpGO=Ysz6015OarFf2t0-Yc7WZt8MNnQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sat, 6 Jun 2020 at 14:12, Cedric Leong <cedricleong(at)gmail(dot)com> 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 complaint would have more meaning if you'd mentioned which
version of PostgreSQL you're using. The performance of partitioning in
PostgreSQL has changed significantly over the past 3 releases. Also
would be useful to know what you've actually done (actual commands).
I can't imagine it makes *everything* slower, so it might be good to
mention what is actually slower.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cedric Leong | 2020-06-06 02:49:46 | Re: Date vs Timestamp without timezone Partition Key |
| Previous Message | Cedric Leong | 2020-06-06 02:12:26 | Re: Date vs Timestamp without timezone Partition Key |