Re: Unexpected behaviour: it was documented to return the same value

Ok. Yes, changing the existing behaviour could lead to back compatibility issues. But have you found the functionality to "make an option unrecognizable again" useful? In theory, would it be appropriate to have eg. "UNSET" to perform that?

Re: Add example to sort results by two composite types

.   Кому: kes-...@yandex.ru (kes-...@yandex.ru), pgsql-docs@lists.postgresql.org (pgsql-docs@lists.postgresql.org); Тема: Add example to sort results by two composite types; 14.07.2025, 16:58

Re: Unexpected behaviour: it was documented to return the same value

lists.postgresql.org); Тема: Unexpected behaviour: it was documented to return the same value; 13.07.2025, 16:34, "KES" : I would prefer to remove the option from the configuration list instead of havin

Re: Unexpected behaviour: it was documented to return the same value

fault. How to make it "unrecognizable" again using set_config/RESET? The exact problem I am trying to resolve was asked here: https://stackoverflow.com/q/50923911/4632019  Кому: kes-...@yandex.ru (kes-...@yandex.ru), pgsql-docs@lists.postgr

Re: Ambiguous usage of 'any' in explanation

>or NULL if any of the comparisons result in unknownresult in unknown?? 13.10.2018, 00:37, "David G. Johnston" :On Fri, Oct 12, 2018 at 8:04 AM Bruce Momjian wrote:Sorry, but I don't like this wording.  The problem is that the comparison has two row sets --- the left-hand side, a

Re: Ambiguous usage of 'any' in explanation

either it is hard to understand. I will rephrase one part to show how it is easy to understand from my side:>ALL> The result is “false” if any false result is found. The result of ALL is "false" even if *at least one*  row yield false(we can use 'some' word here, but it is not such clear as *at lea

Re: Ambiguous usage of 'any' in explanation

-   The result is NULL if the comparison does not return true for any row,+   The result is NULL if no comparison with a subquery row returns true,    and it returns NULL for at least one row.-The result of ANY is “true” if the comparison returns true for any subquery row. The result is “false” if

Re: Documentation does not cover multiple WITH in one query

Thank you. That is I am looking for. Never thought that 'WITH' syntax is described at 'SELECT'. Will be very helpful if this will be mentioned on this page: https://www.postgresql.org/docs/10/static/queries-with.html For an example: [ WITH [ RECURSIVE ] with_query [, ...] ] and with_q