Message-ID: <51CC73B6.2050406@optionshouse.com>
Date: Thu, 27 Jun 2013 12:17:42 -0500
From: Shaun Thomas <sthomas@optionshouse.com>
Reply-To: <sthomas@optionshouse.com>
Organization: Peak6
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Igor Neyman <ineyman@perceptron.com>
CC: "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: Partitions not Working as Expected
References: <51CC652F.3010304@optionshouse.com>
 <A76B25F2823E954C9E45E32FA49D70EC1BBD8EEA@mail.corp.perceptron.com>
In-Reply-To: 
 <A76B25F2823E954C9E45E32FA49D70EC1BBD8EEA@mail.corp.perceptron.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
content-transfer-encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

On 06/27/2013 12:08 PM, Igor Neyman wrote:

> Doesn't have to be hardcoded.
> If executed as dynamic sql, it will be re-planned properly, e.g.:

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.

So now I get to tell our devs to refactor six years of JAVA code and 
find any place they use CURRENT_DATE, and replace it with an ORM 
variable for the current date instead.

At this point I wonder why CURRENT_DATE even exists, if using it is 
apparently detrimental to query execution.

-- 
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-676-8870
sthomas@optionshouse.com

______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance