On Mon, May 7, 2018 at 06:14:02PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/static/functions-json.html
> Description:
>
> Hi team,
>
> I had the following issue when going through your
>
On Wed, May 9, 2018 at 02:25:28PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/static/app-psql.html
> Description:
>
> While I get that we want alphabetical order an exception for \i and \ir
While creating the release notes, I was confused by the description for
strict_word_similarity(), particularly "extent boundaries". The
attached patch clarifies, at least for me, how word_similarity() and
strict_word_similarity() differ.
--
Bruce Momjian http://momjian.us
Enterprise
> Uh, why would we list \ir before the simpler \i?
I believe the OP was complaining that the current order is:
\i or \include filename
(text)
\if expression
\elif expression
\else
\endif
(longer text)
\ir or \include_relative filename
(text)
and that before it was:
\i or
"Vianello, Daniel A" writes:
>> Uh, why would we list \ir before the simpler \i?
> So that the request is to merge \ir into the \i section (not before \i but
> part of that discusstion) rather than being separated by the comparatively
> longer section for \if
It was, in fact, like that initia
