| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Edson Richter <edsonrichter(at)hotmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Range partitioning and overlap |
| Date: | 2020-11-13 20:32:52 |
| Message-ID: | CAKFQuwavKNFu5oAL4c36uuoWgsMBteSrBBxOg4nrPYoXokHYmw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-general |
On Fri, Nov 13, 2020 at 1:29 PM Edson Richter <edsonrichter(at)hotmail(dot)com>
wrote:
> "Range Partitioning
>
> The table is partitioned into “ranges” defined by a key column or set of
> columns, with no overlap between the ranges of values assigned to different
> partitions. For example, one might partition by date ranges, or by ranges
> of identifiers for particular business objects."
> Is there a misinterpretation from my side, or examples are inconsistent
> with the paragraph above?
>
Further on the documentation: "When creating a range partition, the lower
bound specified with FROM is an inclusive bound, whereas the upper bound
specified with TO is an exclusive bound."
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Edson Richter | 2020-11-13 20:46:43 | RE: Range partitioning and overlap |
| Previous Message | Edson Richter | 2020-11-13 20:29:22 | Range partitioning and overlap |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2020-11-13 20:45:56 | Re: New "function tables" in V13 documentation |
| Previous Message | Edson Richter | 2020-11-13 20:29:22 | Range partitioning and overlap |