The pages of pg_dump, pg_dumpall and pg_upgrade mentioned that their
--no-statistics and --statistics options did not include the handling of
statistics created by CREATE STATISTICS, which was wrong.
Oversight in
c32fb29e979d.
Reported-by: Igi Izumi <igi@sraoss.co.jp>
Discussion: https://postgr.es/m/19529-
c7eb1e7a0b07eae6@postgresql.org
When <option>--statistics</option> is specified,
<command>pg_dump</command> will include most optimizer statistics in the
resulting dump file. This does not include all statistics, such as
- those created explicitly with <xref linkend="sql-createstatistics"/>,
custom statistics added by an extension, or statistics collected by the
cumulative statistics system. Therefore, it may still be useful to
run <command>ANALYZE</command> after restoring from a dump file to ensure
When <option>--statistics</option> is specified,
<command>pg_dumpall</command> will include most optimizer statistics in the
resulting dump file. This does not include all statistics, such as
- those created explicitly with <xref linkend="sql-createstatistics"/>,
custom statistics added by an extension, or statistics collected by the
cumulative statistics system. Therefore, it may still be useful to
run <command>ANALYZE</command> on each database after restoring from a dump
Unless the <option>--no-statistics</option> option is specified,
<command>pg_upgrade</command> will transfer most optimizer statistics
from the old cluster to the new cluster. This does not transfer
- all statistics, such as those created explicitly with
- <xref linkend="sql-createstatistics"/>, custom statistics added by
+ all statistics, such as custom statistics added by
an extension, or statistics collected by the cumulative statistics system.
</para>