From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Marc Millas <marc(dot)millas(at)mokadb(dot)com> |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: how to "explain" some ddl |
Date: | 2020-07-14 17:05:14 |
Message-ID: | 2875990.1594746314@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Marc Millas <marc(dot)millas(at)mokadb(dot)com> writes:
> We would like to understand where an alter table attach partition spend its
> time.
> to my understanding, explain doesnt do this.
Nope :-(. As our DDL commands have gotten more complicated, there's
been some discussion of adding that, but nothing's really been done
yet.
There is some progress-monitoring support for some DDL commands now,
but that's not quite the same thing.
> for a BI job we have a partitionned table with 1800+ partitions.
TBH I'd recommend scaling that down by at least a factor of ten.
We are not at a point where you can expect that all operations will
be cheap even with thousands of partitions. We may never be at that
point, although people continue to chip away at the bottlenecks.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Radoslav Nedyalkov | 2020-07-14 17:29:03 | single table - fighting a seq scan |
Previous Message | Michael Nolan | 2020-07-14 17:03:41 | Problem with FDW wrapper errors |