Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UsGjp-0006WT-K7 for pgsql-performance@arkaria.postgresql.org; Thu, 27 Jun 2013 18:16:09 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1UsGjp-00070w-4F for pgsql-performance@arkaria.postgresql.org; Thu, 27 Jun 2013 18:16:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UsGjo-00070q-BR for pgsql-performance@postgresql.org; Thu, 27 Jun 2013 18:16:08 +0000 Received: from smtp2.peak6.com ([38.98.137.9]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UsGjj-0004dH-96 for pgsql-performance@postgresql.org; Thu, 27 Jun 2013 18:16:08 +0000 X-AuditID: 0a02cb20-b7f216d000002f75-e9-51cc8161e76e Received: from sswchi5pcas2.peak6.net (Unknown_Domain [10.100.13.24]) by smtp2.peak6.com (Symantec Messaging Gateway) with SMTP id 26.78.12149.1618CC15; Thu, 27 Jun 2013 13:16:01 -0500 (CDT) Received: from [10.10.201.64] (10.10.201.64) by sswchi5pcas2.peak6.net (10.100.13.25) with Microsoft SMTP Server (TLS) id 14.3.123.3; Thu, 27 Jun 2013 13:16:00 -0500 Message-ID: <51CC8160.2080905@optionshouse.com> Date: Thu, 27 Jun 2013 13:16:00 -0500 From: Shaun Thomas Reply-To: 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: Dave Johansen CC: bricklen , "pgsql-performance@postgresql.org" Subject: Re: Partitions not Working as Expected References: <51CC652F.3010304@optionshouse.com> <51CC73B6.2050406@optionshouse.com> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed content-transfer-encoding: 7bit X-Originating-IP: [10.10.201.64] X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCKsWRmVeSWpSXmKPExsXClcIroZvYeCbQ4EK7mMX6jwdZLf63/WG0 uD7zHLMDs8fOWXfZPS7sm8YewBTVwGiTmJeXX5JYkqqQklqcbKvkX1CSmZ9X7JFfWpyq4JJZ nJyTmJmbWqSkkJliq2SspFCQk5icmpuaV2KrlFhQkJqXomTHpYABbIDKMvMUUvOS81My89Jt lTyD/XUtLEwtdQ2V7OKRQUInS8b1eb8YCx4wVzxqM21g/MfUxcjJISFgInF10mFGCFtM4sK9 9WxdjFwcQgIHGCV+bG9ngXBWMkr83baQFaSKV0Bf4viVdywgNouAqsSSry/BJrEJ6EpM6l/B BmILCahI9J29ARbnFxCW2PehiRnEFhUIk3i/bCrUHEGJkzOfAM3h4BAR0JL4tM4BJMwskCXx 7v51sHJhAUuJa8u3QN2wkEni57uP7CAJToFAial/f7FBNNhKXJhznQXClpfY/nYOM8QNqhIr mieyQXymIPH/yjumCYwis5CsnoWkfRaS9gWMzKsYxYvLEpMzMs0KinNLCoz0ClITs8308lJL NjGCop7ptMIOxs09VocYBTgYlXh4J+SfCRRiTSwrrsw9xCjBwawkwnvEHyjEm5JYWZValB9f VJqTWnyI0QcYZhOZpUST84EJKa8k3tDY1MDU0tTQ1NzU0AiHsJI47z6mZYFCAunA5JOdmlqQ WgQzjomDU6qBsWXhjteuU943VCzpehw3R3JtdZzswYmv2K58vPnrjdg7/+N2Tw79e2cjnd5m IcO1ljngQESCxq4Du1f0PeHwqY2cmKSplvDr5JEaq2aWK4sP+2v/MFxjdHBFuemRpylzLhhz HLOSt49i/nhjXk8c6xMbyeCtHPExWd9nXD8SFrX3rn3D8tcP/iqxFGckGmoxFxUnAgCKgGf9 JwMAAA== X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On 06/27/2013 12:42 PM, Dave Johansen wrote: > Or what about something like DATE_TRUNC("DAY", now())? Or would that run > into the same optimization/planner problems as CURRENT_DATE? Same issue. This seems to work, though I'm not entirely sure of the implications: UPDATE pg_proc SET provolatile = 'i' WHERE proname = 'date_in'; -- 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