mirror of
https://github.com/postgres/postgres.git
synced 2025-08-06 18:42:54 +03:00
Remove whitespace from end of lines
pgindent and perltidy should clean up the rest.
This commit is contained in:
@@ -188,7 +188,7 @@ hostnossl <replaceable>database</replaceable> <replaceable>user</replaceable>
|
||||
obsolete but still accepted spelling of <literal>samerole</>.)
|
||||
Superusers are not considered to be members of a role for the
|
||||
purposes of <literal>samerole</> unless they are explicitly
|
||||
members of the role, directly or indirectly, and not just by
|
||||
members of the role, directly or indirectly, and not just by
|
||||
virtue of being a superuser.
|
||||
The value <literal>replication</> specifies that the record
|
||||
matches if a replication connection is requested (note that
|
||||
|
@@ -9648,8 +9648,8 @@ table2-mapping
|
||||
<literal>array_to_json(anyarray [, pretty_bool])</literal>
|
||||
</entry>
|
||||
<entry>
|
||||
Returns the array as JSON. A Postgres multi-dimensional array
|
||||
becomes a JSON array of arrays. Line feeds will be added between
|
||||
Returns the array as JSON. A Postgres multi-dimensional array
|
||||
becomes a JSON array of arrays. Line feeds will be added between
|
||||
dimension 1 elements if pretty_bool is true.
|
||||
</entry>
|
||||
<entry><literal>array_to_json('{{1,5},{99,100}}'::int[])</literal></entry>
|
||||
@@ -9663,7 +9663,7 @@ table2-mapping
|
||||
<literal>row_to_json(record [, pretty_bool])</literal>
|
||||
</entry>
|
||||
<entry>
|
||||
Returns the row as JSON. Line feeds will be added between level
|
||||
Returns the row as JSON. Line feeds will be added between level
|
||||
1 elements if pretty_bool is true.
|
||||
</entry>
|
||||
<entry><literal>row_to_json(row(1,'foo'))</literal></entry>
|
||||
@@ -13812,7 +13812,7 @@ SELECT pg_type_is_visible('myschema.widget'::regtype);
|
||||
<row>
|
||||
<entry><literal><function>pg_get_viewdef(<parameter>view_name</parameter>, <parameter>pretty_bool</>)</function></literal></entry>
|
||||
<entry><type>text</type></entry>
|
||||
<entry>get underlying <command>SELECT</command> command for view,
|
||||
<entry>get underlying <command>SELECT</command> command for view,
|
||||
lines with fields are wrapped to 80 columns if pretty_bool is true (<emphasis>deprecated</emphasis>)</entry>
|
||||
</row>
|
||||
<row>
|
||||
@@ -13823,13 +13823,13 @@ SELECT pg_type_is_visible('myschema.widget'::regtype);
|
||||
<row>
|
||||
<entry><literal><function>pg_get_viewdef(<parameter>view_oid</parameter>, <parameter>pretty_bool</>)</function></literal></entry>
|
||||
<entry><type>text</type></entry>
|
||||
<entry>get underlying <command>SELECT</command> command for view,
|
||||
<entry>get underlying <command>SELECT</command> command for view,
|
||||
lines with fields are wrapped to 80 columns if pretty_bool is true</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry><literal><function>pg_get_viewdef(<parameter>view_oid</parameter>, <parameter>wrap_int</>)</function></literal></entry>
|
||||
<entry><type>text</type></entry>
|
||||
<entry>get underlying <command>SELECT</command> command for view,
|
||||
<entry>get underlying <command>SELECT</command> command for view,
|
||||
wrapping lines with fields as specified, pretty printing is implied</entry>
|
||||
</row>
|
||||
<row>
|
||||
|
@@ -1622,7 +1622,7 @@ PostgreSQL, contrib and HTML documentation successfully made. Ready to install.
|
||||
On some systems with shared libraries
|
||||
you need to tell the system how to find the newly installed
|
||||
shared libraries. The systems on which this is
|
||||
<emphasis>not</emphasis> necessary include
|
||||
<emphasis>not</emphasis> necessary include
|
||||
<systemitem class="osname">FreeBSD</>,
|
||||
<systemitem class="osname">HP-UX</>, <systemitem
|
||||
class="osname">IRIX</>, <systemitem class="osname">Linux</>,
|
||||
|
@@ -270,7 +270,7 @@ gmake prefix=/usr/local/pgsql.new install
|
||||
|
||||
<para>
|
||||
Install any custom shared object files (or DLLs) used by the old cluster
|
||||
into the new cluster, e.g. <filename>pgcrypto.so</filename>,
|
||||
into the new cluster, e.g. <filename>pgcrypto.so</filename>,
|
||||
whether they are from <filename>contrib</filename>
|
||||
or some other source. Do not install the schema definitions, e.g.
|
||||
<filename>pgcrypto.sql</>, because these will be upgraded from the old cluster.
|
||||
|
@@ -403,11 +403,11 @@ PostgreSQL documentation
|
||||
Dump only the object definitions (schema), not data.
|
||||
</para>
|
||||
<para>
|
||||
To exclude table data for only a subset of tables in the database,
|
||||
To exclude table data for only a subset of tables in the database,
|
||||
see <option>--exclude-table-data</>.
|
||||
</para>
|
||||
<para>
|
||||
This option is equivalent to specifying
|
||||
This option is equivalent to specifying
|
||||
<option>--section=pre-data --section=post-data</>.
|
||||
</para>
|
||||
</listitem>
|
||||
@@ -417,13 +417,13 @@ PostgreSQL documentation
|
||||
<term><option>--section=<replaceable class="parameter">sectionname</replaceable></option></term>
|
||||
<listitem>
|
||||
<para>
|
||||
Only dump the named section. The name can be one of <option>pre-data</>, <option>data</>
|
||||
and <option>post-data</>.
|
||||
Only dump the named section. The name can be one of <option>pre-data</>, <option>data</>
|
||||
and <option>post-data</>.
|
||||
This option can be specified more than once. The default is to dump all sections.
|
||||
</para>
|
||||
<para>
|
||||
Post-data items consist of definitions of indexes, triggers, rules
|
||||
and constraints other than validated check constraints.
|
||||
Post-data items consist of definitions of indexes, triggers, rules
|
||||
and constraints other than validated check constraints.
|
||||
Pre-data items consist of all other data definition items.
|
||||
</para>
|
||||
</listitem>
|
||||
@@ -640,7 +640,7 @@ PostgreSQL documentation
|
||||
Do not dump data for any tables matching the <replaceable
|
||||
class="parameter">table</replaceable> pattern. The pattern is
|
||||
interpreted according to the same rules as for <option>-t</>.
|
||||
<option>--exclude-table-data</> can be given more than once to
|
||||
<option>--exclude-table-data</> can be given more than once to
|
||||
exclude tables matching any of several patterns. This option is
|
||||
useful when you need the definition of a particular table even
|
||||
though you do not need the data in it.
|
||||
|
@@ -363,7 +363,7 @@
|
||||
uses the word <quote>schema</> in a different meaning.)
|
||||
</para>
|
||||
<para>
|
||||
This option is equivalent to specifying
|
||||
This option is equivalent to specifying
|
||||
<option>--section=pre-data --section=post-data</>.
|
||||
</para>
|
||||
</listitem>
|
||||
@@ -515,13 +515,13 @@
|
||||
<term><option>--section=<replaceable class="parameter">sectionname</replaceable></option></term>
|
||||
<listitem>
|
||||
<para>
|
||||
Only restore the named section. The name can be one of <option>pre-data</>, <option>data</>
|
||||
and <option>post-data</>.
|
||||
Only restore the named section. The name can be one of <option>pre-data</>, <option>data</>
|
||||
and <option>post-data</>.
|
||||
This option can be specified more than once. The default is to restore all sections.
|
||||
</para>
|
||||
<para>
|
||||
Post-data items consist of definitions of indexes, triggers, rules
|
||||
and constraints other than validated check constraints.
|
||||
Post-data items consist of definitions of indexes, triggers, rules
|
||||
and constraints other than validated check constraints.
|
||||
Pre-data items consist of all other data definition items.
|
||||
</para>
|
||||
</listitem>
|
||||
|
@@ -29,7 +29,7 @@ non-ASCII characters find using grep -P '[\x80-\xFF]'
|
||||
does not support it
|
||||
http://www.pemberley.com/janeinfo/latin1.html#latexta
|
||||
|
||||
do not use numeric _UTF_ numeric character escapes (&#nnn;),
|
||||
do not use numeric _UTF_ numeric character escapes (&#nnn;),
|
||||
we can only use Latin1
|
||||
|
||||
Example: Alvaro Herrera is Álvaro Herrera
|
||||
|
Reference in New Issue
Block a user