From: Shaun Thomas <sthomas@optionshouse.com>
To: Igor Neyman <ineyman@perceptron.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Partitions not Working as Expected
Date: Thu, 27 Jun 2013 12:17:42 -0500
Message-ID: <51CC73B6.2050406@optionshouse.com> (raw)
In-Reply-To: <A76B25F2823E954C9E45E32FA49D70EC1BBD8EEA@mail.corp.perceptron.com>
References: <51CC652F.3010304@optionshouse.com>
<A76B25F2823E954C9E45E32FA49D70EC1BBD8EEA@mail.corp.perceptron.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sthomas@optionshouse.com, ineyman@perceptron.com
Subject: Re: Partitions not Working as Expected
In-Reply-To: <51CC73B6.2050406@optionshouse.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox