Re: Convert Existing Table to a Partition Table in PG10
| От | Clifford Snow |
|---|---|
| Тема | Re: Convert Existing Table to a Partition Table in PG10 |
| Дата | |
| Msg-id | CADAoPLowhpMKfOniMy2Sg3ei=G=NZXt80K4UTsj3EvjD6+_mUQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Convert Existing Table to a Partition Table in PG10 (David Rowley <david.rowley@2ndquadrant.com>) |
| Ответы |
Re: Convert Existing Table to a Partition Table in PG10
|
| Список | pgsql-general |
David,
Thanks for the suggestion. That really simplifies creating the RANGE.
For all, I'm pretty much a postgresql novice, but I've tried to document what I've learned in the hopes that it can help someone else.
You can read my blog post at https://osm_seattle.snowandsnow.us/articles/Partitioning-Postgresql/
Clifford
On Sun, Jul 1, 2018 at 2:23 PM David Rowley <david.rowley@2ndquadrant.com> wrote:
On 1 July 2018 at 10:15, Clifford Snow <clifford@snowandsnow.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
В списке pgsql-general по дате отправления: