Re: Range partitioning and overlap

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: Range partitioning and overlap
Дата
Msg-id CAKFQuwbndKUsbZ=kAHhAgkbgZoMC8stcY648-ntAWqcpUtdgtg@mail.gmail.com
обсуждение исходный текст
Ответ на RE: Range partitioning and overlap  (Edson Richter <edsonrichter@hotmail.com>)
Список pgsql-general
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:


David J.

В списке pgsql-general по дате отправления:

Предыдущее
От: "David G. Johnston"
Дата:
Сообщение: Re: Restoring database from false update
Следующее
От: Morris de Oryx
Дата:
Сообщение: ERROR: could not find tuple for statistics object - is there a way to clean this up?