Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dhO7V-0006At-8D for pgsql-performance@arkaria.postgresql.org; Mon, 14 Aug 2017 22:46:01 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dhO7U-0004OJ-Qw for pgsql-performance@arkaria.postgresql.org; Mon, 14 Aug 2017 22:46:00 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dhO5h-0001Dq-V4 for pgsql-performance@postgresql.org; Mon, 14 Aug 2017 22:44:10 +0000 Received: from mail-it0-x231.google.com ([2607:f8b0:4001:c0b::231]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dhO5a-00035O-TY for pgsql-performance@postgresql.org; Mon, 14 Aug 2017 22:44:09 +0000 Received: by mail-it0-x231.google.com with SMTP id 77so2424940itj.1 for ; Mon, 14 Aug 2017 15:44:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bowt-ie.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IZL2TUnEBcHhKEDe8E/5tFFNAmzuLa1HO1V0prEFUFc=; b=yH6ScfsOw0MDqjX61aKxDOt0jaK1bsmW3AeDIvVh276K16W9f2O6OfVbgdTJHC+q9i mPRTj27hNIfouHwHmO5qsrKDYsjR7HAMRE/CaD4YBBCkrkE3I27Q3L+BZ0reEu6DDhpP wTVVKLAnG7YbuJTAKBkv4AU5ZAd88U1eqnGDGsgW91Nh5nOnvC5aGl2H+MK+cLpiuXKX VIs+2pL9DZvcm7UTPYa0qy8DFqiBtBTlMRrXuPk2qyIpxpABpFL2hOy8HOudUiM1nZ9Z nUpOV5mGvSIqczX9ux6kMEfSUiR5UJJBZIULzgqrcbaWV84lJhHhYAwyw7YZ4bHcSE1L qMtA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IZL2TUnEBcHhKEDe8E/5tFFNAmzuLa1HO1V0prEFUFc=; b=QPzZBchWMzVravHkwwRRbZOFXg/lPGFYMImnX8YL5BVO78nxe1pVOdlR7hmHesOL+6 112Hnz0bSt86Hlfu5CvgAKIzUm17UbGJoz2+voMnimVqTJQ7WHXg3C68GN2fjjKObdlR 6xJ5mOOAyfmbYAUfDHArzdI2NROPhm1UqBror6dciYTK/+G4o7dbt9Msl//EAT3+7f+V Qn2/pd9GZkdGgvsoNzckpubSGQUbPfMIOxLdaFJKWozC1iwGN5QXqaa4okfuTBDW7aik 8tWvch6j+JQMIbDtPaN8QK/5tsG/GE5L9bfPmTnnKhz4ZrSRSHNTauP6w2jWGvIUjjAQ FMFw== X-Gm-Message-State: AHYfb5hA21ROKTN4NyrMCvJgKSfdjZmmK3Aebx0DM/gkyi3R8JU9TbtE 9CsqM8wV0i1jj8AIRv+qjbFtUneJr47o X-Received: by 10.36.219.11 with SMTP id c11mr475952itg.108.1502750640936; Mon, 14 Aug 2017 15:44:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.2.79.219 with HTTP; Mon, 14 Aug 2017 15:43:40 -0700 (PDT) In-Reply-To: References: From: Peter Geoghegan Date: Mon, 14 Aug 2017 15:43:40 -0700 Message-ID: Subject: Re: Odd sudden performance degradation related to temp object churn To: Jeremy Finzel Cc: postgres performance list Content-Type: text/plain; charset="UTF-8" List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org On Mon, Aug 14, 2017 at 12:53 PM, Jeremy Finzel 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? -- Peter Geoghegan -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance