On Sat, May 16, 2020 at 09:38:46PM +0300, Marina Polyakova wrote:
> I like if we can explain the situation in more detail. But IMO the phrase
> "same as default" sounds as if we will try to find the primary index and use
> it if the required index (with pg_index.indisreplident = true) does not
> ex
> No, it's not the example but the operator description, and what it says
> is
> "string || non-string or non-string || string"
>
> so it's trying to illustrate that there are two options:
>
> string || non-string
> non-string || string
I see, that makes a lot more sense.
> but maybe it's not s
PG Doc comments form writes:
> The second line in "Table 9.8. SQL String Functions and Operators" uses
> "non-string or non-string" as part of the example. I assume one of these
> should be "string".
It might look that way depending on how wide your browser window is...
but the way it's supposed
On 2020-May-17, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/11/functions-string.html
> Description:
>
> The second line in "Table 9.8. SQL String Functions and Operators" uses
> "non-string or non-str
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/functions-string.html
Description:
The second line in "Table 9.8. SQL String Functions and Operators" uses
"non-string or non-string" as part of the example. I assume one of these
should b
