Re: Explain Analyze (Rollback off) Suggestion - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Explain Analyze (Rollback off) Suggestion
Date
Msg-id 6667.1590677567@sss.pgh.pa.us
Whole thread Raw
In response to Re: Explain Analyze (Rollback off) Suggestion  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Explain Analyze (Rollback off) Suggestion
List pgsql-hackers
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> The ANALYZE option should not be part of the GUC setup.

Yeah.  While I'm generally not in favor of putting GUCs into the mix
here, the only one that seriously scares me is a GUC that would affect
whether the EXPLAIN'd query executes or not.  A GUC that causes buffer
counts to be reported/not-reported is not going to result in data
destruction when someone forgets that it's on.

(BTW, adding an option for auto-rollback wouldn't change my opinion
about that.  Not all side-effects of a query can be rolled back.  Thus,
if there is an auto-rollback option, it mustn't be GUC-adjustable
either.)

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Resolving the python 2 -> python 3 mess
Next
From: "David G. Johnston"
Date:
Subject: Re: Explain Analyze (Rollback off) Suggestion