Re: Query Plan Performance on Partitioned Table

From: Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com>
To: Rural Hunter <ruralhunter(at)gmail(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Query Plan Performance on Partitioned Table
Date: 2015-08-11 13:53:06
Message-ID: CAK-MWwSM1rs8K4FB5-04o1NXpJYz93+LS46WLsvz0UuWQOXTuA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Aug 11, 2015 at 11:44 PM, Rural Hunter <ruralhunter(at)gmail(dot)com>
wrote:

> # \dt+
> ​​
> article_729
> List of relations
> Schema | Name | Type | Owner | Size | Description
> --------+-------------+-------+--------+--------+-------------
> public | article_729 | table | omuser1 | 655 MB |
> (1 row)
> The problem exists on not only this specific child table, but with all of
> them.
>

​Oops sorry, оf course I mean "\d+​
​ article_729
​" (to see criteria used for partitioning).​

--
Maxim Boguk
Senior Postgresql DBA
http://www.postgresql-consulting.ru/ <http://www.postgresql-consulting.com/>

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Rural Hunter 2015-08-11 14:00:52 Re: Query Plan Performance on Partitioned Table
Previous Message Rural Hunter 2015-08-11 13:44:14 Re: Query Plan Performance on Partitioned Table