doc_only_relevant.patch
text/x-patch
Filename: doc_only_relevant.patch
Type: text/x-patch
Part: 0
Patch
Same data as JSON:
GET /api/v1/attachments/:id/patch
the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes.
API reference →
Format: unified
| File | + | − |
|---|---|---|
| doc/src/sgml/datatype.sgml | 1 | 1 |
| doc/src/sgml/ref/pg_dumpall.sgml | 2 | 2 |
| doc/src/sgml/ref/pg_dump.sgml | 2 | 2 |
| doc/src/sgml/ref/pg_restore.sgml | 2 | 2 |
diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index 71cf59e..02763b5 100644
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -3596,7 +3596,7 @@ SELECT person.name, holidays.num_weeks FROM person, holidays
as the canonical form for MAC addresses, and specifies the first
form (with colons) as the bit-reversed notation, so that
08-00-2b-01-02-03 = 01:00:4D:08:04:0C. This convention is widely
- ignored nowadays, and it is only relevant for obsolete network
+ ignored nowadays, and it is relevant only for obsolete network
protocols (such as Token Ring). PostgreSQL makes no provisions
for bit reversal, and all accepted formats use the canonical LSB
order.
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index 4503830..b19f15e 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -427,7 +427,7 @@ PostgreSQL documentation
<listitem>
<para>
Specify the superuser user name to use when disabling triggers.
- This is only relevant if <option>--disable-triggers</> is used.
+ This is relevant only if <option>--disable-triggers</> is used.
(Usually, it's better to leave this out, and instead start the
resulting script as superuser.)
</para>
@@ -602,7 +602,7 @@ PostgreSQL documentation
<term><option>--disable-triggers</></term>
<listitem>
<para>
- This option is only relevant when creating a data-only dump.
+ This option is relevant only when creating a data-only dump.
It instructs <application>pg_dump</application> to include commands
to temporarily disable triggers on the target tables while
the data is reloaded. Use this if you have referential
diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml
index 7c49c03..253ee01 100644
--- a/doc/src/sgml/ref/pg_dumpall.sgml
+++ b/doc/src/sgml/ref/pg_dumpall.sgml
@@ -190,7 +190,7 @@ PostgreSQL documentation
<listitem>
<para>
Specify the superuser user name to use when disabling triggers.
- This is only relevant if <option>--disable-triggers</> is used.
+ This is relevant only if <option>--disable-triggers</> is used.
(Usually, it's better to leave this out, and instead start the
resulting script as superuser.)
</para>
@@ -283,7 +283,7 @@ PostgreSQL documentation
<term><option>--disable-triggers</></term>
<listitem>
<para>
- This option is only relevant when creating a data-only dump.
+ This option is relevant only when creating a data-only dump.
It instructs <application>pg_dumpall</application> to include commands
to temporarily disable triggers on the target tables while
the data is reloaded. Use this if you have referential
diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml
index b276da6..2993369 100644
--- a/doc/src/sgml/ref/pg_restore.sgml
+++ b/doc/src/sgml/ref/pg_restore.sgml
@@ -383,7 +383,7 @@
<listitem>
<para>
Specify the superuser user name to use when disabling triggers.
- This is only relevant if <option>--disable-triggers</> is used.
+ This is relevant only if <option>--disable-triggers</> is used.
</para>
</listitem>
</varlistentry>
@@ -458,7 +458,7 @@
<term><option>--disable-triggers</></term>
<listitem>
<para>
- This option is only relevant when performing a data-only restore.
+ This option is relevant only when performing a data-only restore.
It instructs <application>pg_restore</application> to execute commands
to temporarily disable triggers on the target tables while
the data is reloaded. Use this if you have referential