Subject: Re: Partitioning by month causing an error?
To: pgsql-admin@lists.postgresql.org
References: 
 <CAOC+FBW=zSLyHWg2XDTp2eeEAmwzkzZLQPBqFx7_Cso=WMK3ew@mail.gmail.com>
From: Ron <ronljohnsonjr@gmail.com>
Message-ID: <ff56245a-1be6-fbc0-e60c-295c5adec50b@gmail.com>
Date: Fri, 20 Dec 2019 20:24:44 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: 
 <CAOC+FBW=zSLyHWg2XDTp2eeEAmwzkzZLQPBqFx7_Cso=WMK3ew@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Precedence: bulk

On 12/20/19 6:49 PM, Wells Oliver wrote:
> I have a partition per each month, like this:
>
> CREATE TABLE mmd_yr2019_3 PARTITION OF mmd FOR VALUES FROM ('2019-03-01') 
> TO ('2019-03-31');
> CREATE TABLE mmd_yr2019_4 PARTITION OF mmd FOR VALUES FROM ('2019-04-01') 
> TO ('2019-04-30');
>
> This breaks for dates at the end of the month. What's the better way to 
> write the bounds? 3/1 to 4/1 and then 4/1 to 5/1? Does that cause some 
> overlap issue?

What is the mmd data type?  I ask that because '2019-03-31' is really 
'2019-03-31 00:00:00.000', so there's nowhere for '2019-03-31 00:00:00.001' 
through '2019-03-31 23:59:59.999' to go.  (And don't forget timezones.)


-- 
Angular momentum makes the world go 'round.