Re: Are there tuning parameters that don't take effect immediately?

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Michael Nolan <htfoot(at)gmail(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Are there tuning parameters that don't take effect immediately?
Date: 2015-06-12 20:52:33
Message-ID: CAKFQuwZMX10xq2HVhim1rgrrFLwdc+NN1ko4GTXY5VkCpZsLMA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, Jun 12, 2015 at 4:37 PM, Michael Nolan <htfoot(at)gmail(dot)com> wrote:

> The only thing I can come up that's happened since last night was that we
> ran the nightly vacuum analyze on that database, but I did not change the
> statistics target.
>

​The answer to your question is no, parameters changes are worse would take
effect after a reboot - though most are used on the very next query that
runs.

The vacuum would indeed likely account for the gains - there being
significantly fewer ​dead/invisible rows to have to scan over and discard
while retrieving the live rows that fulfill your query.

David J.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Joshua D. Drake 2015-06-12 21:00:28 Re: Are there tuning parameters that don't take effect immediately?
Previous Message Michael Nolan 2015-06-12 20:37:00 Are there tuning parameters that don't take effect immediately?