From: Jerry Sievers <gsievers19@comcast.net>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Jeremy Finzel <finzelj@gmail.com>,
  postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: Odd sudden performance degradation related to temp object churn
References: 
 <CAMa1XUi6pbugdB7zUA6weoPjmUHTzNLZcSEAh06-7FZRzkuHQw@mail.gmail.com>
	<CAH2-WznKCt_UBaPEY=WwBof+TkTaDYHbZmDsFE=Vigy3Rqi35A@mail.gmail.com>
Date: Mon, 14 Aug 2017 18:10:38 -0500
In-Reply-To: 
 <CAH2-WznKCt_UBaPEY=WwBof+TkTaDYHbZmDsFE=Vigy3Rqi35A@mail.gmail.com>
	(Peter Geoghegan's message of "Mon, 14 Aug 2017 15:43:40 -0700")
Message-ID: <87mv71eoep.fsf@jsievers.enova.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

Peter Geoghegan <pg@bowt.ie> writes:

> On Mon, Aug 14, 2017 at 12:53 PM, Jeremy Finzel <finzelj@gmail.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.consulting@comcast.net
p: 312.241.7800


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