Re: Partitions not Working as Expected

From: bricklen <bricklen(at)gmail(dot)com>
To: sthomas(at)optionshouse(dot)com
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Partitions not Working as Expected
Date: 2013-06-27 17:34:30
Message-ID: CAGrpgQ_3pCLt3CJnap3z+nWe3-Q=A3sMH7OKP0sUeo79kViD8w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Jun 27, 2013 at 10:17 AM, Shaun Thomas <sthomas(at)optionshouse(dot)com>wrote:

>
> Well yeah. That's not really the point, though. Aside from existing code,
> hard-coding is generally frowned upon. Our devs have been using
> CURRENT_DATE and its ilk for over six years now.
>

Would it help to put the current_date call in a wrapper function and coerce
it as IMMUTABLE? A quick test shows that constraint exclusion seems to kick
in, but I can't speak intelligently about whether that is wise or not.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Dave Johansen 2013-06-27 17:42:13 Re: Partitions not Working as Expected
Previous Message Shaun Thomas 2013-06-27 17:17:42 Re: Partitions not Working as Expected