From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | Jeremy Finzel <finzelj(at)gmail(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Odd sudden performance degradation related to temp object churn |
Date: | 2017-08-14 23:10:38 |
Message-ID: | 87mv71eoep.fsf@jsievers.enova.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> On Mon, Aug 14, 2017 at 12:53 PM, Jeremy Finzel <finzelj(at)gmail(dot)com> wrote:
>
>> This particular db is on 9.3.15. Recently we had a serious performance
>> degradation related to a batch job that creates 4-5 temp tables and 5
>> indexes. It is a really badly written job but what really confuses us is
>> that this job has been running for years with no issue remotely approaching
>> this one. We are also using pgpool.
>
> Did you happen to notice that this occurred when you upgrading point
> release? If so, what version did you move from/to?
The system was last started back in November. Running 9.3.15.
Not aware of any host system libs or whatever change recently but will investigate.
>
> --
> Peter Geoghegan
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800
From | Date | Subject | |
---|---|---|---|
Next Message | Mariel Cherkassky | 2017-08-15 10:06:40 | Re: performance problem on big tables |
Previous Message | Peter Geoghegan | 2017-08-14 22:43:40 | Re: Odd sudden performance degradation related to temp object churn |