tables have merged columns

2020-11-13 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/13/functions-json.html Description: In this version i cannot see columns https://www.postgresql.org/docs/13/functions-json.html in older versions are columns seen correctly https://www.postg

Re: tables have merged columns

2020-11-13 Thread David G. Johnston
On Friday, November 13, 2020, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/13/functions-json.html > Description: > > In this version i cannot see columns > https://www.postgresql.org/docs/13/functions-j

Partitioning docs (was Re: Range partitioning and overlap)

2020-11-13 Thread Tom Lane
[ redirecting to pgsql-docs ] I wrote: > 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

Re: Partitioning docs (was Re: Range partitioning and overlap)

2020-11-13 Thread David G. Johnston
On Fri, Nov 13, 2020 at 7:13 PM Tom Lane wrote: > [ redirecting to pgsql-docs ] > > I wrote: > > 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

Re: Partitioning docs (was Re: Range partitioning and overlap)

2020-11-13 Thread Tom Lane
"David G. Johnston" writes: > Looks good to me (just read the patch), Thanks! Just one suggestion toward > the top: > ...allows you to (specify declaratively => declare) that a table is divided > into partitions. (specification becomes declaration further down) Sure. That's a little further fr