The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/tutorial-join.html
Description:
Actually, it is good practice to avoid using 'cross joins' and use the
'inner join' syntax. Most query planners might optimize both queries to run
the
Euler Taveira writes:
> It seems an oversight. I'm attaching patches to fix it in all supported
> branches. v11 can be applied cleanly to v12/master.
Ah, I'd already done this before seeing your response :-(
regards, tom lane
PG Doc comments form writes:
> Page: https://www.postgresql.org/docs/12/indexes-expressional.html
> It appears as if the paragraph beginning: "If we were to declare this index
> UNIQUE..."
> actually belongs just before the paragraph beginning: "Expression indexes
> also allow control over..."
>
PG Doc comments form writes:
> This page says that "CREATE GROUP is now an alias for CREATE ROLE.",
> But when u check the CREATE ROLE, u see they have different options,
The implementations are the same, as you could easily find by experiment.
Looks like people have been sloppy about updating
On Fri, 10 Apr 2020 at 08:19, PG Doc comments form
wrote:
>
> This page says that "CREATE GROUP is now an alias for CREATE ROLE.",
> But when u check the CREATE ROLE, u see they have different options,
> I don't know if this is on purpose or not, But if it's just an alias, then
> they should
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/indexes-expressional.html
Description:
It appears as if the paragraph beginning: "If we were to declare this index
UNIQUE..."
actually belongs just before the paragraph beginning:
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/sql-creategroup.html
Description:
Hello,
This page says that "CREATE GROUP is now an alias for CREATE ROLE.",
But when u check the CREATE ROLE, u see they have different options,
I don't
