From: Justin Pryzby <pryzby@telsasoft.com>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: pgsql-hackers@postgresql.org
Subject: should check interrupts in BuildRelationExtStatistics ?
Date: Sun, 8 May 2022 19:01:08 -0500
Message-ID: <20220509000108.GQ28830@telsasoft.com> (raw)
Restarting a large instance took twice as long as I expected due to not
checking interrupts in (at least) statext_ndistinct_build. Long enough that I
attached (and was able to attach) a debugger to verify, which I think is too
long. I think it could cause issues for an high-availability cluster or other
script if it takes too long to shut down.
The tables being auto-analyzed have 9 exteneded stats objects, each with stats
target=10. 7 of those are (ndistinct) stats on 4 simple columns plus 1
expression (5 total). And the other 2 stats objects are expressional stats
(necessarily on a single expression).
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: pgsql-hackers@postgresql.org
Cc: pryzby@telsasoft.com, tomas.vondra@enterprisedb.com
Subject: Re: should check interrupts in BuildRelationExtStatistics ?
In-Reply-To: <20220509000108.GQ28830@telsasoft.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox