Doc: fix a couple of erroneous examples.

The example given for anyelement <@ anymultirange didn't return
true as claimed; adjust it so it does.

In passing, change a couple of sample results where the modern
numeric-based logic produces a different number of trailing zeroes
than before.

Erik Rijkers

Discussion: https://postgr.es/m/cc35735d-1ec1-5bb3-9e27-cddbab7afa23@xs4all.nl
This commit is contained in:
Tom Lane 2022-06-01 10:39:46 -04:00
parent f2a0060a9b
commit 80cd99c558
1 changed files with 3 additions and 3 deletions

View File

@ -1046,7 +1046,7 @@ repeat('Pg', 4) <returnvalue>PgPgPgPg</returnvalue>
</para>
<para>
<literal>@ -5.0</literal>
<returnvalue>5</returnvalue>
<returnvalue>5.0</returnvalue>
</para></entry>
</row>
@ -1463,7 +1463,7 @@ repeat('Pg', 4) <returnvalue>PgPgPgPg</returnvalue>
</para>
<para>
<literal>log(2.0, 64.0)</literal>
<returnvalue>6.0000000000</returnvalue>
<returnvalue>6.0000000000000000</returnvalue>
</para></entry>
</row>
@ -18536,7 +18536,7 @@ SELECT NULLIF(value, '(none)') ...
Is the element contained by the multirange?
</para>
<para>
<literal>42 &lt;@ '{[1,7)}'::int4multirange</literal>
<literal>4 &lt;@ '{[1,7)}'::int4multirange</literal>
<returnvalue>t</returnvalue>
</para></entry>
</row>