> On Nov 18, 2021, at 2:42 PM, Tom Lane wrote:
>
> This is all guesswork though, since we don't know quite what's
> happening on Robert's system. It might be worth setting
> "log_autovacuum_min_duration = 0" (either globally, or as a
> reloption on the relevant tables), and seeing if there see
On Nov 18, 2021, at 2:08 PM, Thomas Munro
mailto:thomas.mu...@gmail.com>> wrote:
This message originated outside your organization.
On Fri, Nov 19, 2021 at 6:03 AM Robert Creager
mailto:robe...@spectralogic.com>> wrote:
Which would be better? Discard plans or forcing custom plans? Seems lik
Thomas Munro writes:
> I'm wondering if the thing that changed between 9.6 and 13 might be
> the heuristics for when auto vacuum's background ANALYZE is triggered,
> creating the unlucky timing required to get your system to this state
> occasionally.
> For a while now I have been wondering how w
On Fri, Nov 19, 2021 at 6:03 AM Robert Creager wrote:
> Which would be better? Discard plans or forcing custom plans? Seems like
> wrapping a copy might be better than the Postgres.conf change as that would
> affect all statements. What kind of performance hit would we be taking with
> that
> On Nov 17, 2021, at 10:42 PM, Justin Pryzby wrote:
>
> This message originated outside your organization.
>
> On Thu, Nov 18, 2021 at 04:39:42PM +1300, Thomas Munro wrote:
>> On Thu, Nov 18, 2021 at 1:18 PM Robert Creager
>> wrote:
>>> So, how do I go about capturing more information for
