<structname>production_publication</structname>:
<programlisting>
ALTER PUBLICATION production_publication ADD TABLE users, departments, ALL TABLES IN SCHEMA production;
-</programlisting>
- </para>
+</programlisting></para>
</refsect1>
<refsect1>
</para>
</listitem>
</varlistentry>
- </variablelist>
- </para>
+ </variablelist></para>
</listitem>
</varlistentry>
</para>
</listitem>
</varlistentry>
- </variablelist>
- </para>
+ </variablelist></para>
</listitem>
</varlistentry>
</para>
</listitem>
</varlistentry>
- </variablelist>
- </para>
+ </variablelist></para>
</listitem>
</varlistentry>
</para>
<para>
- <indexterm>
- <primary>trigger</primary>
- <secondary>constraint trigger</secondary>
- </indexterm>
When the <literal>CONSTRAINT</literal> option is specified, this command creates a
- <firstterm>constraint trigger</firstterm>. This is the same as a regular trigger
+ <firstterm>constraint trigger</firstterm>.<indexterm><primary>trigger</primary>
+ <secondary>constraint trigger</secondary></indexterm>
+ This is the same as a regular trigger
except that the timing of the trigger firing can be adjusted using
<link linkend="sql-set-constraints"><command>SET CONSTRAINTS</command></link>.
Constraint triggers must be <literal>AFTER ROW</literal> triggers on plain
However, the last example would be ambiguous if there is also, say,
<programlisting>
CREATE PROCEDURE do_db_maintenance(IN target_schema text, IN options text) ...
-</programlisting>
- </para>
+</programlisting></para>
</refsect1>
<refsect1 id="sql-dropprocedure-compatibility">
the action's event type.
</para>
</listitem>
- </orderedlist>
- </para>
+ </orderedlist></para>
</listitem>
- </orderedlist>
- </para>
+ </orderedlist></para>
</listitem>
<listitem>
<para>
directory <filename>backup</filename>:
<screen>
<prompt>$</prompt> <userinput>pg_basebackup -D backup -Ft --compress=gzip:9</userinput>
-</screen>
- </para>
+</screen></para>
</refsect1>
<para>
Here is some example output with following options:
<screen>
-pgbench --aggregate-interval=10 --time=20 --client=10 --log --rate=1000
---latency-limit=10 --failures-detailed --max-tries=10 test
-</screen>
+<userinput>pgbench --aggregate-interval=10 --time=20 --client=10 --log --rate=1000
+--latency-limit=10 --failures-detailed --max-tries=10 test</userinput>
-<screen>
1649114136 5815 27552565 177846919143 1078 21716 2756787 7264696105 0 9661 0 7854 31472 4022 4022 0
1649114146 5958 28460110 182785513108 1083 20391 2539395 6411761497 0 7268 0 8127 32595 4101 4101 0
</screen>
0.582 3363 41576 UPDATE pgbench_branches SET bbalance = bbalance + :delta WHERE bid = :bid;
0.465 0 0 INSERT INTO pgbench_history (tid, bid, aid, delta, mtime) VALUES (:tid, :bid, :aid, :delta, CURRENT_TIMESTAMP);
1.933 0 0 END;
- </screen>
- </para>
+</screen></para>
<para>
If multiple script files are specified, all statistics are reported
supposed to never occur...).
</para>
</listitem>
- </itemizedlist>
- </para>
+ </itemizedlist></para>
</listitem>
<listitem>
<para>