public inbox for [email protected]
help / color / mirror / Atom feedFrom: Yugo Nagata <[email protected]>
To: Ryohei Takahashi (Fujitsu) <[email protected]>
Cc: 'David Rowley' <[email protected]>
Cc: [email protected] <[email protected]>
Cc: Corey Huinker <[email protected]>
Subject: Re: Can we use Statistics Import and Export feature to perforamance testing?
Date: Thu, 23 Oct 2025 19:27:53 +0900
Message-ID: <[email protected]> (raw)
In-Reply-To: <TY3PR01MB11891C649F6B4406994EC972982B52@TY3PR01MB11891.jpnprd01.prod.outlook.com>
References: <TY3PR01MB118914FCCBBDC126C34AA287382B52@TY3PR01MB11891.jpnprd01.prod.outlook.com>
<CAApHDvozyyTc19zhnWSqMhvW_dqYJCCkdh5mo3DA65zEFPu8fg@mail.gmail.com>
<TY3PR01MB11891C649F6B4406994EC972982B52@TY3PR01MB11891.jpnprd01.prod.outlook.com>
Hi,
On Tue, 8 Apr 2025 12:14:08 +0000
"Ryohei Takahashi (Fujitsu)" <[email protected]> wrote:
> Thank you for your reply.
> I understand that the access plans are not guaranteed to be the same.
>
> Can we add these notes to the pg_dump page in the PostgreSQL Documentation
> in order to prevent users from asking the same question?
I agree that it would be helpful to add this description, since the wording
“statistics manipulation functions” might give the impression that they can
influence generated plans.
I’ve attached a patch that adds a new paragraph to the warning section of the
documentation on statistics manipulation functions:
Manually restored statistics do not guarantee that the same query plans
will be generated as in the source environment, since factors such as
relation sizes, index OIDs, and configuration parameters may affect
planner behavior.
What do you think?
Regards,
Yugo Nagata
--
Yugo Nagata <[email protected]>
Attachments:
[text/x-diff] doc_add_warning_on_stats_manipulation_funcs.patch (738B, 2-doc_add_warning_on_stats_manipulation_funcs.patch)
download | inline diff:
diff --git a/doc/src/sgml/func/func-admin.sgml b/doc/src/sgml/func/func-admin.sgml
index 1b465bc8ba7..bbdd20571d4 100644
--- a/doc/src/sgml/func/func-admin.sgml
+++ b/doc/src/sgml/func/func-admin.sgml
@@ -1959,6 +1959,12 @@ postgres=# SELECT '0/0'::pg_lsn + pd.segment_number * ps.setting::int + :offset
<command>VACUUM</command> or <command>ANALYZE</command>) and should be
considered temporary.
</para>
+ <para>
+ Manually restored statistics do not guarantee that the same query plans
+ will be generated as in the source environment, since factors such as
+ relation sizes, index OIDs, and configuration parameters may affect
+ planner behavior.
+ </para>
</warning>
</para>
view thread (8+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Can we use Statistics Import and Export feature to perforamance testing?
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox