From: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Partitioning by month causing an error? |
Date: | 2019-12-21 02:32:02 |
Message-ID: | CAOC+FBXwJuW_rrjb=RzhoRcMfRYrx6GfyO9b53guQe1DVPZZPw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
mmd has a PARTITION BY RANGE on a date column.
On Fri, Dec 20, 2019 at 6:24 PM Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
> 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.
>
>
>
--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2019-12-21 02:36:22 | Re: Partitioning by month causing an error? |
Previous Message | Ron | 2019-12-21 02:24:44 | Re: Partitioning by month causing an error? |