Re: Enabling constraint_exclusion does not avoid scanning all child partitions

From: "Fayza Sultan" <fayza(dot)sultan(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: Enabling constraint_exclusion does not avoid scanning all child partitions
Date: 2006-12-03 22:37:37
Message-ID: 38443e510612031437h30337dejc928f059fb5fa79c@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Your point solved my problem.

Thank you

-Fayza

On 12/4/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Fayza Sultan" <fayza(dot)sultan(at)gmail(dot)com> writes:
> > CREATE TABLE parent (
> > monthdate date NOT NULL,
> > id int4 NOT NULL,
> > CONSTRAINT parent_idx PRIMARY KEY (monthdate,id )
> > );
>
> > CREATE TABLE child1
> > (
> > CONSTRAINT child1_idx PRIMARY KEY (monthdate,id),
> > CONSTRAINT child1_chk CHECK (monthdate >= '2006-01-01
> 00:00:00'::timestamp
> > without time zone AND monthdate < '2006-02-01 00:00:00'::timestamp
> without
> > time zone)
>
> monthdate is date, not timestamp. See the caveat in the documentation
> about avoiding cross-type comparisons when formulating constraints for
> constraint exclusion to use.
>
> regards, tom lane
>

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Carlo Stonebanks 2006-12-04 05:16:22 Is Vacuum/analyze destroying my performance?
Previous Message Tom Lane 2006-12-03 22:25:27 Re: Enabling constraint_exclusion does not avoid scanning all child partitions