From: | Rural Hunter <ruralhunter(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Very slow planning performance on partition table |
Date: | 2014-07-25 03:26:03 |
Message-ID: | 53D1CE4B.4020104@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-performance |
2014/7/25 9:53, Tom Lane wrote:
> Rural
> [ shrug... ] Insufficient data. When I try a simple test case based on
> what you've told us, I get planning times of a couple of milliseconds.
> I can think of contributing factors that would increase that, but not by
> four orders of magnitude. So there's something very significant that
> you've left out. Can you construct a self-contained test case that's
> this slow?
>
> regards, tom lane
>
No I cann't. I exported the db schema(without data) to another server
and there is no problem. Is the planning time related to data volume?
Anything else can I check? I already checked the default statistics
target and it's the default value. I did change some statistics target
on one column of the table, but the column is not involved in the slow
planning query.
From | Date | Subject | |
---|---|---|---|
Next Message | Rural Hunter | 2014-07-25 14:23:49 | Re: Very slow planning performance on partition table |
Previous Message | Tom Lane | 2014-07-25 01:53:23 | Re: Very slow planning performance on partition table |
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2014-07-25 09:19:54 | Re: Debugging writing load |
Previous Message | Tom Lane | 2014-07-25 01:53:23 | Re: Very slow planning performance on partition table |