From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
---|---|
To: | Clifford Snow <clifford(at)snowandsnow(dot)us> |
Cc: | srkrishna(at)yahoo(dot)com, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Convert Existing Table to a Partition Table in PG10 |
Date: | 2018-07-01 21:23:47 |
Message-ID: | CAKJS1f_-zW2LMXrtd6h9O_Bb6YUVS5C2juP7awfd-YC9jR131A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 1 July 2018 at 10:15, Clifford Snow <clifford(at)snowandsnow(dot)us> wrote:
> I also leaned that my range partition value I used on a timestamp needed to
> have fractional seconds. I used a range of 2017-01-01 00:00:00 to
> 2017-23:59:59 which failed when I attempted to add a record that had a
> timestamp of 2017-23:59:59. Adding a fractional second to the range solved
> the problem.
Please be aware that with RANGE partitions the upper bound is
non-inclusive. The lower bound is inclusive.
If you want a 2017 partition, then FOR VALUES FROM ('2017-01-01') TO
('2018-01-01') will allow all 2017 timestamps and only 2017
timestamps.
You've no need to consider precision of the type and how many 9's you
add to anything here.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Clifford Snow | 2018-07-01 23:43:44 | Re: Convert Existing Table to a Partition Table in PG10 |
Previous Message | Francisco Olarte | 2018-07-01 09:00:57 | Re: Convert Existing Table to a Partition Table in PG10 |