Re: Automating Partitions in PostgreSQL - Query on syntax

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: vacuum(at)quantentunnel(dot)de
Cc: Csaba Nagy <nagy(at)ecircle-ag(dot)com>, pgsql-hackers(at)postgresql(dot)org, stark(at)enterprisedb(dot)com, kedar(dot)potdar(at)gmail(dot)com
Subject: Re: Automating Partitions in PostgreSQL - Query on syntax
Date: 2009-04-21 17:38:33
Message-ID: 603c8f070904211038g68e79c5brab7f485dca849e74@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> > The big win that is associated with table partitioning is using
>> > constraint exclusion to avoid unnecessary partitions scans.
>
> there is no reason for not using the 'CASE condition' for constraint exclusion.

There is if you can't rely on the rows to be in the right partition.
Allowing DDL commands to change the partitioning layout without moving
the rows is going cause a lot of problems for you, I think.

I'm also not sure how skillful the constraint exclusion logic is at
proving theorems when CASE statements are involved. It might be good
to test that before going too far with this approach.

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2009-04-21 17:42:51 Re: per db collate syntax
Previous Message Jaime Casanova 2009-04-21 17:37:40 per db collate syntax