Re: rapid degradation after postmaster restart - Mailing list pgsql-performance

From Tom Lane
Subject Re: rapid degradation after postmaster restart
Date
Msg-id 18481.1079192379@sss.pgh.pa.us
Whole thread Raw
In response to rapid degradation after postmaster restart  (Joe Conway <mail@joeconway.com>)
Responses Re: rapid degradation after postmaster restart  (Joe Conway <mail@joeconway.com>)
List pgsql-performance
Joe Conway <mail@joeconway.com> writes:
> ... Immediately
> after a postmaster restart, the first insert or two take about 1.5
> minutes (undoubtedly this could be improved, but it isn't the main
> issue). However by the second or third insert, the time increases to 7 -
> 9 minutes. Restarting the postmaster causes the cycle to repeat, i.e.
> the first one or two inserts are back to the 1.5 minute range.

Just to be clear on this: you have to restart the postmaster to bring
the time back down?  Simply starting a fresh backend session doesn't do
it?

Are you using particularly large values for shared_buffers or any of the
other resource parameters?

            regards, tom lane

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: rapid degradation after postmaster restart
Next
From: Joe Conway
Date:
Subject: Re: rapid degradation after postmaster restart