<programlisting>

max_locks_per_transaction = 256

</programlisting>

<para>Typically, <productname>1C</productname> solutions use a lot of temporary tables. Every backend process usually contains multiple temporary tables. When closing a connection, <productname>&productname;</productname> tries to drop all temporary tables in a singletransactio, so this transaction may use a lot of locks. If the number of locks exceeds the <varname>max_locks_per_transaction</varname> value, the transaction will fail, leaving multiple orphaned temporary tables.

<para>Typically, <productname>1C</productname> solutions use a lot of temporary tables. Every backend process usually contains multiple temporary tables. When closing a connection, <productname>&productname;</productname> tries to drop all temporary tables in a singletransaction, so this transaction may use a lot of locks. If the number of locks exceeds the <varname>max_locks_per_transaction</varname> value, the transaction will fail, leaving multiple orphaned temporary tables.

</para>

</listitem>

</itemizedlist>

<link linkend="catalog-pg-statistic"><structname>pg_statistic</structname></link>

table. The <function>dump_statistic</> function generates <literal>INSERT</>

statements which can later be applied to a compatible database. The extension

should be installed on the recipient server in order tosuccessfuly restore

should be installed on the recipient server in order tosuccessfully restore

statistical data since these statements heavily rely on the provided functions.

</para>

<para>

The <productname>&productname;</productname> equivalence operator is

defined to return NULL when both operands are NULLs. However, the Microsoft

SQL Servers familytraditionaly defines other semantic for equivalence

SQL Servers familytraditionally defines other semantic for equivalence

operator, where operator returns TRUE in the case of both nulled operands.

This module provides such operator with MSSQL semantic.

</para>

</listitem>

<listitem>

<simpara><application>plantuner</application> module provides hits for planner, which can do disable or enable indexes for query execution.</simpara>

</listitem>

</listitem>

<listitem>

<simpara><application>pg_tsparser</application> module is an alternative text search parser.</simpara>

</listitem>

</itemizedlist>

</para>

Unfortunately, jsonb have no statistics yet. That's why JsQuery

optimizer has to do imperative decision while selecting

conditions to be evaluated using index. This decision is made by

assumtion that some condition types are less selective than

assumption that some condition types are less selective than

others. Optimizer divides conditions into following selectivity

class (listed by descending of selectivity).

</para>

</para>

<para>

It implements types MCHAR and MVARCHAR, which are bug-to-bug

compatible with MSSQL CHAR and VARCHAR respectively.Additionaly,

these types use libicu forcomparation and case conversion, so their

compatible with MSSQL CHAR and VARCHAR respectively.Additionally,

these types use libicu forcomparison and case conversion, so their

behavior is identical across different operating systems.

</para>

<para>

<itemizedlist>

<listitem>

<para>

Case insensitivecomparation

Case insensitivecomparison

</para>

</listitem>

<listitem>

<listitem>

<para>

Time &mdash; time it took topeform the backup.

Time &mdash; time it took toperform the backup.

</para>

</listitem>

<title>Overview</title>

<para>

Each nonutility query statement (SELECT/INSERT/UPDATE/DELETE) after

optimization/planning stage is translated into plan tree wich is kind of

optimization/planning stage is translated into plan tree, which is kind of

imperative representation of declarative SQL query. EXPLAIN ANALYZE

request allows to demonstrate execution statistics gathered from each

node of plan tree (full time of execution, number of rows emitted to upper

</listitem>

<listitem>

<para>

format - EXPLAIN format to be used for plans printing,posible values:

format - EXPLAIN format to be used for plans printing,possible values:

text, xml, json, yaml.

</para>

</listitem>

</para>

<para>

Calling role have to be superuser or member of the role whose backend is

being called.Othrewise function prints ERROR message

being called.Otherwise function prints ERROR message

<literal>permission denied</literal>.

</para>

</sect2>

index on the column or group of columns used in the constraint.

Optional clause <literal>INCLUDE</literal> allows to add into the index

a portion of columns on which the uniqueness is not enforced upon.

Note, thatalthogh constraint is not enforced upon included columns, it still

Note, thatalthough constraint is not enforced upon included columns, it still

depends on them. Consequently, some operations on these columns (e.g. <literal>DROP COLUMN</literal>)

can cause cascade constraint and index deletion.

See paragraph about <literal>INCLUDE</literal> in

index on the column or group of columns used in the constraint.

An optional clause <literal>INCLUDE</literal> allows to add into the index

a portion of columns on which the constraint is not enforced upon.

Note, thatalthogh constraint is not enforced upon included columns, it still

Note, thatalthough constraint is not enforced upon included columns, it still

depends on them. Consequently, some operations on these columns (e.g. <literal>DROP COLUMN</literal>)

can cause cascade constraint and index deletion.

See paragraph about <literal>INCLUDE</literal> in

<term><replaceable class="PARAMETER">delay</replaceable></term>

<listitem>

<para>

Timein milisecondstowaiting for LSN to be replayed.

Time towait for LSN to be replayed, in milliseconds.

</para>

</listitem>

</varlistentry>

<para>

Delay time to waiting for LSN to be replayed must be integer. For

default it is infinity. Waiting can beinterupped using Ctl+C, or

default it is infinity. Waiting can beinterrupted using Ctl+C, or

by Postmaster death.

</para>

</refsect1>

use of <xref linkend="pgupgrade">, is required for those

wishing to migrate data from any previous release.</para>

<para>Dump/restore is notneccessary when migrating from PostgreSQL 9.6.x to

<para>Dump/restore is notnecessary when migrating from PostgreSQL 9.6.x to

Postgres Pro 9.6.x.y.</para>

<para>When upgrading from previous releases of Postgres Pro or from

<para>

Typically, DBA would play with queries interactively, and save

their plans and then enable use of saved plans for the queries,

where predictableresponce time is essential.

where predictableresponse time is essential.

</para>

<para>

Then application which uses these queries would use saved plans.

<literal>_p()</> function.

</para>

<programlisting>

=&gt;update sr_plans set enable = true wherequesry=

=&gt;update sr_plans set enable = true wherequery=

'select a,b from test_table where a = _p(1)';

UPDATE 1

-- These queries would use saved plan