The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/view-pg-stats.html
Description:
First paragraph for the pg_stats view says: "This view allows access only to
rows of pg_statistic that correspond to tables the user has permission to
read,
On Friday, December 8, 2023, Gulyás Attila wrote:
>
> Unfortunately, neither the row constructor docs[7] nor the pages
> referenced there mention this usage anywhere (unless I missed it somehow).
> I also found this answer[8] helpful when trying to find the relevant docs.
>
I found this fairly,q
Hi,
I asked this on Stackoverflow[0] months ago, and finally posting it here as
well, along with Laurenz Albe's helpful comments:
The query `SELECT * FROM table WHERE NOT (table IS NOT NULL);` finds all
the rows in `table` that have a `null` value in any column. This answer[1]
helped understand t
Ah, I just misread it. I think it's perfectly clear actually, I just went there
looking for the default order (ASC/DESC) and skimmed the first line about ORDER
BY. I must have interpreted "whatever order" to mean "whichever orientation of
ordering".
Sorry about that.
Zane
_
On Fri, 8 Dec 2023 at 22:49, PG Doc comments form
wrote:
> Page: https://www.postgresql.org/docs/16/sql-select.html
> Description:
>
> At the top of the sql-select page it says
>
> "If ORDER BY is not given, the rows are returned in whatever order the
> system finds fastest to produce."
>
> but la
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/sql-select.html
Description:
At the top of the sql-select page it says
"If ORDER BY is not given, the rows are returned in whatever order the
system finds fastest to produce."
but later
