From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Edson Richter <edsonrichter(at)hotmail(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Range partitioning and overlap |
Date: | 2020-11-13 20:58:04 |
Message-ID: | 398613.1605301084@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-general |
Edson Richter <edsonrichter(at)hotmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Edson Richter | 2020-11-13 21:08:06 | RE: Range partitioning and overlap |
Previous Message | Edson Richter | 2020-11-13 20:46:43 | RE: Range partitioning and overlap |
From | Date | Subject | |
---|---|---|---|
Next Message | Edson Richter | 2020-11-13 21:08:06 | RE: Range partitioning and overlap |
Previous Message | Maksim Fomin | 2020-11-13 20:56:38 | Restoring database from false update |