Re: [PERFORM] Postgres partitions-query scanning all child tables

2016-01-28 Thread rverghese
Yeah that would be a pain to have the date_part in each query. Thanks for the info! Date: Thu, 28 Jan 2016 00:48:10 -0700 From: ml-node+s1045698n5884581...@n5.nabble.com To: ri...@hotmail.com Subject: Re: Postgres partitions-query scanning all child tables On Thu, Jan 28, 2016 at 1:10

Re: [PERFORM] Postgres partitions-query scanning all child tables

2016-01-27 Thread Corey Huinker
On Wed, Jan 27, 2016 at 5:09 PM, rverghese wrote: > Hi I have a master table and the inherited tables broken up by month. > > /e.g. CONSTRAINT transactions_january_log_date_check CHECK > (date_part('month'::text, log_date) = 1::double precision);/ > > So transactions_master

Re: [PERFORM] Postgres partitions-query scanning all child tables

2016-01-27 Thread rverghese
Ok, thanks. Thats a bummer though. That means I need a table for every month/year combination. I was hoping to limit it to 12 tables. Riya Date: Wed, 27 Jan 2016 21:31:35 -0700 From: ml-node+s1045698n5884560...@n5.nabble.com To: ri...@hotmail.com Subject: Re: Postgres partitions-query scanning

Re: [PERFORM] Postgres partitions-query scanning all child tables

2016-01-27 Thread Corey Huinker
On Thu, Jan 28, 2016 at 1:10 AM, rverghese wrote: > Ok, thanks. Thats a bummer though. That means I need a table for every > month/year combination. I was hoping to limit it to 12 tables. > > Riya > > If you wanted to have a column called month_num or something like that, and