Re: Postgres partitions-query scanning all child tables

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: rverghese <riyav(at)hotmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Postgres partitions-query scanning all child tables
Date: 2016-01-28 07:47:20
Message-ID: CADkLM=dYPBgHLtsEzgW+kxepCnyvOeENxvB2rywoEHTW0EDj1A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Jan 28, 2016 at 1:10 AM, rverghese <riyav(at)hotmail(dot)com> wrote:

> Ok, thanks. Thats a bummer though. That means I need a table for every
> month/year combination. I was hoping to limit it to 12 tables.
>
> Riya
>
>
If you wanted to have a column called month_num or something like that, and
if *all* of your queries extract the month date_part() in every where
clause, then yes, you could have just 12 tables.

But you won't like that partitioning scheme for other reasons:
- queries that don't "play by the rules" will be slow
- very old data will slow down recent-day queries
- no ability to quickly remove obsolete data by dropping partitions that
are no longer useful

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message rverghese 2016-01-28 19:51:38 Re: Postgres partitions-query scanning all child tables
Previous Message rverghese 2016-01-28 06:10:35 Re: Postgres partitions-query scanning all child tables