From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: rapid degradation after postmaster restart |
Date: | 2004-03-13 15:39:39 |
Message-ID: | 18481.1079192379@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Joe Conway <mail(at)joeconway(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2004-03-13 15:45:35 | Re: Log rotation |
Previous Message | Fernando Nasser | 2004-03-13 15:36:23 | Re: Log rotation |
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2004-03-13 15:51:48 | Re: rapid degradation after postmaster restart |
Previous Message | Tom Lane | 2004-03-13 04:02:35 | Re: rapid degradation after postmaster restart |