gen_random_uuid random source clarification

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/17/functions-uuid.html Description: In reference to the documentation for gen_random_uuid at: https://www.postgresql.org/docs/17/functions-uuid.html It would be good to add a comment about th

Re: Possible documentation inaccuracy in optimizer README

On Wed, 9 Apr 2025 at 14:33, Tom Lane wrote: > Maybe better: > > Other possibilities will be excluded for lack of join clauses. > (In reality, use of EquivalenceClasses would allow us to > deduce additional join clauses that allow more join > combinations, but here

Re: generated constraint name

Peter Eisentraut writes: > On 07.04.25 15:34, David G. Johnston wrote: >> I feel like that whole parenthetical should just go away. The point of >> the comment is to remind the user of how identifier values work with >> respect to mandatory double quoting. The name itself, other than having >

Re: generated constraint name

On 07.04.25 15:34, David G. Johnston wrote: On Sunday, April 6, 2025, PG Doc comments form > wrote: The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/17/ddl-alter.html Description: url:

Missing "each" in `NegotiateProtocolVersion` protocol message format description

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/17/protocol-message-formats.html Description: Dear Postgres Team, There seems to be a missing "each" in documentation for the `NegotiateProtocolVersion` message format: *Then, for [each] pro