Re: Unclear wording
On Fri, 2025-07-11 at 16:12 +, PG Doc comments form wrote: > Page: https://www.postgresql.org/docs/17/ddl-schemas.html > Description: > > In §5.10.3 these two sentences seem inconsistent: > > > When objects are referenced in any other context without schema > qualification...the search path is traversed until a matching object is > found. Therefore, in the default configuration, any unqualified access again > can only refer to the public schema. > > Either unqualified access can refer to any schema in the search path, > because the search path is traversed until a matching object is found, or > else unqualified access can only refer to the public schema because the > search path will not be traversed looking in other schemas for a matching > object, but both of those possibilities conflict with one or the other of > the sentences quoted from the manual. > > Obviously I'm missing something; I don't know which of the two sentences > quoted from the manual to believe, or if I am to understand both are true, > what I am misunderstanding about their meaning. I don't see an inconsistency. The key phrase is "in the default configuration". The default value for 'search_path' is '"$user", public'. Now by default there is no schema with the same name as the database user, so the effective default search path is just the 'public' schema. Yours, Laurenz Albe
Re: Missing File weather.txt
Daniel Gustafsson writes: > Or perhaps ”values are separated by a tab character”? WFM regards, tom lane
Re: Missing File weather.txt
Fujii Masao writes: > On 2025/07/12 7:18, Daniel Gustafsson wrote: >> It should, fixed in v3. > LGTM. Thanks! I'm okay with this too. I find myself niggling a bit at the parenthetical remark "the white space on each line is actually a tab character". There's several tabs on each line, so use of the singular isn't quite right. However, the best alternative phrasing I could come up with is "each instance of white space is actually a single tab character", and that doesn't seem any more understandable. So maybe it's best left as you have it. regards, tom lane
Re: Missing File weather.txt
> On 12 Jul 2025, at 18:23, Tom Lane wrote: > > Fujii Masao writes: >>> On 2025/07/12 7:18, Daniel Gustafsson wrote: >>> It should, fixed in v3. > >> LGTM. Thanks! > > I'm okay with this too. I find myself niggling a bit at the > parenthetical remark "the white space on each line is actually a tab > character". There's several tabs on each line, so use of the singular > isn't quite right. However, the best alternative phrasing I could > come up with is "each instance of white space is actually a single tab > character", and that doesn't seem any more understandable. So maybe > it's best left as you have it. Or perhaps ”values are separated by a tab character”? ./daniel
Re: Missing File weather.txt
> On 12 Jul 2025, at 18:41, Tom Lane wrote: > > Daniel Gustafsson writes: >> Or perhaps ”values are separated by a tab character”? > > WFM Thanks, I'll get this pushed once the freeze is over on REL_18_STABLE. -- Daniel Gustafsson
Unclear wording
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/17/ddl-schemas.html Description: In §5.10.3 these two sentences seem inconsistent: > When objects are referenced in any other context without schema qualification...the search path is traversed until a matching object is found. Therefore, in the default configuration, any unqualified access again can only refer to the public schema. Either unqualified access can refer to any schema in the search path, because the search path is traversed until a matching object is found, or else unqualified access can only refer to the public schema because the search path will not be traversed looking in other schemas for a matching object, but both of those possibilities conflict with one or the other of the sentences quoted from the manual. Obviously I'm missing something; I don't know which of the two sentences quoted from the manual to believe, or if I am to understand both are true, what I am misunderstanding about their meaning.
please define 'statement' in the glossary
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/17/glossary.html Description: Hello, the glossary (https://www.postgresql.org/docs/current/glossary.html) does not define 'statement' but a definition would be important to understand other chapters such as this sentence: "statement_timestamp() returns the start time of the current statement (more specifically, the time of receipt of the latest command message from the client)." The sentence is from https://www.postgresql.org/docs/17/functions-datetime.html#FUNCTIONS-DATETIME-CURRENT. From the same page is this snippet: "start of current statement", in Table 9.33. Date/Time Functions. It seems 'statement' can mean different things such as 'one operation, such as a SELECT statement', but it can also mean 'all operations since the last command message from the client, which can be several SELECTs'. Thank you Peter
the docs for NOTIFY do not mention the global lock that NOTIFY takes
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/17/sql-notify.html Description: The authors of the following article got stuck and had to read postgres' source code to realize that NOTIFY takes a global instance lock: https://www.recall.ai/blog/postgres-listen-notify-does-not-scale https://news.ycombinator.com/item?id=44490510 It may be useful to mention that in https://www.postgresql.org/docs/current/sql-notify.html
