On Fri, Nov 13, 2020 at 2:08 PM Edson Richter
wrote:
> *De:* Tom Lane
> *Enviado:* sexta-feira, 13 de novembro de 2020 17:58
> *Para:* Edson Richter
> *Cc:* David G. Johnston ; pgsql-general <
> pgsql-gene...@postgresql.org>
> *Assunto:* Re: Range partitioning and o
De: Tom Lane
Enviado: sexta-feira, 13 de novembro de 2020 17:58
Para: Edson Richter
Cc: David G. Johnston ; pgsql-general
Assunto: Re: Range partitioning and overlap
Edson Richter writes:
> Further on the documentation: "When creating a range partition, the lower
> bound specifie
Edson Richter writes:
> 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."
> I'm pretty sure I cannot find this statement in PostgreSQL 13 documentation
De: David G. Johnston
Enviado: sexta-feira, 13 de novembro de 2020 17:32
Para: Edson Richter
Cc: pgsql-general
Assunto: Re: Range partitioning and overlap
On Fri, Nov 13, 2020 at 1:29 PM Edson Richter
mailto:edsonrich...@hotmail.com>> wrote:
"Range Partitioning
The table is parti
On Fri, Nov 13, 2020 at 1:29 PM Edson Richter
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 b
Hi,
Using PostgreSQL 13.1 - I need your guidance about corretly implementing
partition by timestamp ranges.
Looking at documentation (
https://www.postgresql.org/docs/13/ddl-partitioning.html ) there a statement
saying explicit
"Range Partitioning
The table is partitioned into “ranges” defin
