Re: how to "explain" some ddl - Mailing list pgsql-general

From Marc Millas
Subject Re: how to "explain" some ddl
Date
Msg-id CADX_1aYuUR0822A5h7PJz1p51kQDLD1nRXEQ8JhJz8gpQGah1g@mail.gmail.com
Whole thread Raw
In response to Re: how to "explain" some ddl  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: how to "explain" some ddl
List pgsql-general
Hi Tom,
a few tests later.
Looks like when you add a partition as default, all tupples of it are read, even if there is an index on the column that is the partition key.
this do explain our attach time. We are going to clean the default partition...

regards,

Marc MILLAS
Senior Architect
+33607850334



On Tue, Jul 14, 2020 at 7:05 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Marc Millas <marc.millas@mokadb.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

pgsql-general by date:

Previous
From: Radoslav Nedyalkov
Date:
Subject: Re: single table - fighting a seq scan
Next
From: Adrian Klaver
Date:
Subject: Re: Problem with FDW wrapper errors