Re: SELECT List with/without parentheses

On Thursday, September 4, 2025, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/17/sql-select.html > Description: > > Here: https://www.postgresql.org/docs/current/sql-select.html > > There is no mention o

Adding clarification on extension_control_path when extension is present in multiple folders

When playing with the new GUC extension_control_path, I found that the paths are evaluated one by one (like search_path)and if an extension is present in multiple paths, only the on in the first path will be considered.I think this is totally fine, but I'd like to adda documentation patch to exp

Re: SELECT List with/without parentheses

PG Doc comments form writes: > There is no mention of the difference in PostgreSql behavior if the select > list of columns is surrounded by parentheses or not. What you've written there is an implicit row constructor, that is "(a,b,...)" is taken as "ROW(a,b,...)". These are documented at [1],

SELECT List with/without parentheses

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/17/sql-select.html Description: Here: https://www.postgresql.org/docs/current/sql-select.html There is no mention of the difference in PostgreSql behavior if the select list of columns is su