RE: Range partitioning and overlap - Mailing list pgsql-general

From Edson Richter
Subject RE: Range partitioning and overlap
Date
Msg-id DM6PR13MB3988A66E9D2BCCD499B550ABCFE60@DM6PR13MB3988.namprd13.prod.outlook.com
Whole thread Raw
In response to Re: Range partitioning and overlap  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Range partitioning and overlap  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
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.

                        regards, tom lane

Thanks!

Regards,

Edson

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Range partitioning and overlap
Next
From: Atul Kumar
Date:
Subject: checkpoint occurs too frequently