Re: Range partitioning and overlap

David G. Johnston <david.g.johnston@gmail.com>

From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Edson Richter <edsonrichter@hotmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-general <pgsql-general@postgresql.org>
Date: 2020-11-15T04:53:28Z
Lists: pgsql-general, pgsql-docs
On Fri, Nov 13, 2020 at 2:08 PM Edson Richter <edsonrichter@hotmail.com>
wrote:

> *De:* Tom Lane <tgl@sss.pgh.pa.us>
> *Enviado:* sexta-feira, 13 de novembro de 2020 17:58
> *Para:* Edson Richter <edsonrichter@hotmail.com>
> *Cc:* David G. Johnston <david.g.johnston@gmail.com>; pgsql-general <
> pgsql-general@postgresql.org>
> *Assunto:* Re: Range partitioning and overlap
>
> Edson Richter <edsonrichter@hotmail.com> 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 page about partitioning. May be this statement is in another
> page?
>
> It's in the CREATE TABLE reference page.  Seems like it would be a good
> idea to have it also in ddl.sgml's discussion of partitioning, though.
>
>
Patch thread with commit:

https://www.postgresql.org/message-id/DM6PR13MB3988736CF8F5DC5720440231CFE60@DM6PR13MB3988.namprd13.prod.outlook.com

David J.

Commits

  1. Doc: improve partitioning discussion in ddl.sgml.