The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/xfunc-c.html
Description:
There is mention to macro PG_ARGNULL_xxx() which I cannot locate. Aren't you
talking of PG_ARGISNULL(n) ?
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/storage-toast.html
Description:
ALTER TABLE ... SET (toast_tuple_target = N) is not documented in "ALTER
TABLE" SQL commands section.
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/sql-altersequence.html
Description:
Although I can see that table_name in OWNED BY clause can be optionally
schema-qualified by á…źcarefully reading "The specified table must have the
same o
On Mon, Feb 3, 2020 at 05:04:00PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.4/explicit-locking.html
> Description:
>
> Hi
>
> The "13.3.1. Table-level Locks" subsection mentions the follow
On Thu, 2020-03-12 at 08:07 +, PG Doc comments form wrote:
> ALTER TABLE ... SET (toast_tuple_target = N) is not documented in "ALTER
> TABLE" SQL commands section.
No, but the documentation for the SET clause references the "Storage Parameter"
section of CREATE TABLE, and it is referenced the
On Thu, 2020-03-12 at 06:34 +, PG Doc comments form wrote:
> There is mention to macro PG_ARGNULL_xxx() which I cannot locate. Aren't you
> talking of PG_ARGISNULL(n) ?
Indeed.
Here is a patch for that.
Yours,
Laurenz Albe
diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml
index
On Mon, Feb 3, 2020 at 07:09:19PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/12/limits.html
> Description:
>
> Appendix K (PostgreSQL Limits) - doesn't mention the (btree) index row size
> lim
On Thu, Mar 12, 2020 at 5:17 PM Bruce Momjian wrote:
> Sorry for the delay in replying. We do get questions about the btree
> length limit occasionally, but practically the length limit usually
> isn't a problem.
Technically the limitation is documented elsewhere, since it is a
limitation of the