public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jerry Sievers <[email protected]>
To: Peter Geoghegan <[email protected]>
Cc: Jeremy Finzel <[email protected]>
Cc: postgres performance list <[email protected]>
Subject: Re: Odd sudden performance degradation related to temp object churn
Date: Mon, 14 Aug 2017 18:10:38 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAH2-WznKCt_UBaPEY=WwBof+TkTaDYHbZmDsFE=Vigy3Rqi35A@mail.gmail.com>
References: <CAMa1XUi6pbugdB7zUA6weoPjmUHTzNLZcSEAh06-7FZRzkuHQw@mail.gmail.com>
	<CAH2-WznKCt_UBaPEY=WwBof+TkTaDYHbZmDsFE=Vigy3Rqi35A@mail.gmail.com>
List-Unsubscribe:  <mailto:[email protected]?body=unsub%20pgsql-performance>

Peter Geoghegan <[email protected]> writes:

> On Mon, Aug 14, 2017 at 12:53 PM, Jeremy Finzel <[email protected]> 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: [email protected]
p: 312.241.7800


-- 
Sent via pgsql-performance mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Odd sudden performance degradation related to temp object churn
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox