Trim trailing whitespace
This commit is contained in:
parent
ddd7b22b22
commit
bf6e4c3c82
@ -4361,7 +4361,7 @@ SELECT (regexp_match('foobarbequebaz', 'bar.*que'))[1];
|
||||
<para>
|
||||
Some examples:
|
||||
<programlisting>
|
||||
SELECT regexp_matches('foo', 'not there');
|
||||
SELECT regexp_matches('foo', 'not there');
|
||||
regexp_matches
|
||||
----------------
|
||||
(0 rows)
|
||||
|
@ -1175,7 +1175,7 @@ synchronous_standby_names = 'FIRST 2 (s1, s2, s3)'
|
||||
An example of <varname>synchronous_standby_names</> for
|
||||
a quorum-based multiple synchronous standbys is:
|
||||
<programlisting>
|
||||
synchronous_standby_names = 'ANY 2 (s1, s2, s3)'
|
||||
synchronous_standby_names = 'ANY 2 (s1, s2, s3)'
|
||||
</programlisting>
|
||||
In this example, if four standby servers <literal>s1</>, <literal>s2</>,
|
||||
<literal>s3</> and <literal>s4</> are running, transaction commits will
|
||||
|
@ -5941,9 +5941,9 @@ char *PQencryptPasswordConn(PGconn *conn, const char *passwd, const char *user,
|
||||
<listitem>
|
||||
<para>
|
||||
Prepares the md5-encrypted form of a <productname>PostgreSQL</> password.
|
||||
<synopsis>
|
||||
<synopsis>
|
||||
char *PQencryptPassword(const char *passwd, const char *user);
|
||||
</synopsis>
|
||||
</synopsis>
|
||||
<function>PQencryptPassword</> is an older, deprecated version of
|
||||
<function>PQencryptPasswodConn</>. The difference is that
|
||||
<function>PQencryptPassword</> does not
|
||||
|
@ -119,13 +119,13 @@ free_percent | 1.95
|
||||
</table>
|
||||
|
||||
<note>
|
||||
<para>
|
||||
The <literal>table_len</literal> will always be greater than the sum
|
||||
of the <literal>tuple_len</literal>, <literal>dead_tuple_len</literal>
|
||||
and <literal>free_space</literal>. The difference is accounted for by
|
||||
fixed page overhead, the per-page table of pointers to tuples, and
|
||||
padding to ensure that tuples are correctly aligned.
|
||||
</para>
|
||||
<para>
|
||||
The <literal>table_len</literal> will always be greater than the sum
|
||||
of the <literal>tuple_len</literal>, <literal>dead_tuple_len</literal>
|
||||
and <literal>free_space</literal>. The difference is accounted for by
|
||||
fixed page overhead, the per-page table of pointers to tuples, and
|
||||
padding to ensure that tuples are correctly aligned.
|
||||
</para>
|
||||
</note>
|
||||
|
||||
<para>
|
||||
|
Loading…
x
Reference in New Issue
Block a user