You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
calculating the next job start time. Possible values
695
695
are:
696
696
<itemizedlist><listitem>
697
-
<para><literal>success</literal> &mdash transaction has finished successfully.
697
+
<para><literal>success</literal> — transaction has finished successfully.
698
698
</para></listitem><listitem>
699
-
<para><literal>failure</literal> &mdash transaction has failed to finish;.
699
+
<para><literal>failure</literal> — transaction has failed to finish;.
700
700
</para></listitem><listitem>
701
701
<para><literal>running</literal> &mdash
702
702
transaction is in progress. </para></listitem>
703
703
<listitem>
704
-
<para><literal>undefined</literal> &mdash transaction has
704
+
<para><literal>undefined</literal> — transaction has
705
705
not started yet. The last two values should not appear
706
706
inside the user procedure. If you see them, they may
707
707
indicate an internal <filename>pgpro_scheduler</filename>
@@ -843,27 +843,27 @@ schedule.create_job(<parameter>dates</parameter> <type>timestamp with time zone[
843
843
<para>Arguments:</para>
844
844
<itemizedlist>
845
845
<listitem>
846
-
<para><parameter>data</parameter> &mdash a <type>jsonb</type> object defining all the job properties. You do not need to define other parameters if the <parameter>data</parameter> is set. All the
846
+
<para><parameter>data</parameter> — a <type>jsonb</type> object defining all the job properties. You do not need to define other parameters if the <parameter>data</parameter> is set. All the
847
847
available <type>jsonb</type> keys are listed in <xref linkend="pgpro-scheduler-jsonb-keys">.</para>
848
848
<para>Type: <type>jsonb</type></para>
849
849
</listitem>
850
850
<listitem>
851
-
<para><parameter>cron</parameter> &mdash a crontab-like string defining the job schedule.</para>
851
+
<para><parameter>cron</parameter> — a crontab-like string defining the job schedule.</para>
852
852
<para>Type: <type>text</type></para>
853
853
</listitem>
854
854
<listitem>
855
-
<para><parameter>dates</parameter> &mdash the exact date or an array of dates for job execution.</para>
855
+
<para><parameter>dates</parameter> — the exact date or an array of dates for job execution.</para>
856
856
<para>Type: <type>timestamp with time zone</type>, <type>timestamp with time zone[]</type></para>
857
857
</listitem>
858
858
<listitem>
859
-
<para><parameter>commands</parameter> &mdash <acronym>SQL</acronym> statements to execute. You can pass one or more <acronym>SQL</acronym>
859
+
<para><parameter>commands</parameter> — <acronym>SQL</acronym> statements to execute. You can pass one or more <acronym>SQL</acronym>
860
860
statements separated by semicolons, or an array of <acronym>SQL</acronym>
861
861
statements. When passed as an array, <acronym>SQL</acronym> statements are
0 commit comments