Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dhe7w-0003Lr-7K for pgsql-performance@arkaria.postgresql.org; Tue, 15 Aug 2017 15:51:32 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dhe7u-0007hF-Gs for pgsql-performance@arkaria.postgresql.org; Tue, 15 Aug 2017 15:51:30 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dhe7t-0007gj-LU for pgsql-performance@postgresql.org; Tue, 15 Aug 2017 15:51:29 +0000 Received: from mail-qt0-x22c.google.com ([2607:f8b0:400d:c0d::22c]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dhe7p-0005MB-R9 for pgsql-performance@postgresql.org; Tue, 15 Aug 2017 15:51:28 +0000 Received: by mail-qt0-x22c.google.com with SMTP id s6so6519820qtc.1 for ; Tue, 15 Aug 2017 08:51:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HvAsKkRp3kJtFlICGROqTb5nVHaRUguNjbD/rvluQcI=; b=jhF3xYj06/J2Mg6rQ+2ArMmZzDSqxQ1+Vz5BVe0ZuISBZBzHOj4HXMzivaWKHEzjhL mI1siq70CM+nOoPz/ht+hGJH1KKxq+61rSuWyWqW7J6xUAglcf/K1gnLFX10kDBM/LY4 0fEXFu817mzKquqBhdjzlLm8y9GQ3/MCIEIBARB2l/m77Iz5WygFVYqggtgd5yTVbwcc 6A7EcSyZQ3xEZ8TI3J/DBe5d6xdWRwomaEFWawC7+ejfbnW1m/qiIna1liPz5JB1Ec2g K56bYng7huZZKui25lq/6M3/AXYfuHdu0pV3tkgMqzUan7riHsdTs/Pz8EHBgEjudNMm xE5g== 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=HvAsKkRp3kJtFlICGROqTb5nVHaRUguNjbD/rvluQcI=; b=AjAUpnRgWLzZHaL/OWeaL74lRfBSb1zcAtiYeyuhr6AVztIGZvi3MNdQxWAJpgsbrN 3kb+3C4zGvoTkol2AIvGz2pHRl/Oz9+ax3mM2gm57QVC8JRm4mfWo9PL1HC2BYVqdIdf MZxYGnpxzfBK/+MXeXdranE1RdUYj2pjyVVuhxhHkxeRKylLocNW3XcZYC8iCxMbJoeR FEHSYQyngNEnjtHZ/B5/xj2tD8b8Tos9Ft86Fz6tyHeJgwfyQJ9aP3yDyg8dFZEcVAJh J1/5YmZixEjFqzaWaDWGauPTM6Pmfx37Qo7UGTwPDudOCJPrC499sjCfr9DdbwWnaFDD gJOg== X-Gm-Message-State: AHYfb5hqNxX4EqHo9O7R3C0qTNDUC2Tbukkut1hF6qm9zoxroP6a8nor TuBJMw6QkO4BZ3QSoih/qDATK2Hstw== X-Received: by 10.200.8.232 with SMTP id y37mr36462152qth.329.1502812284689; Tue, 15 Aug 2017 08:51:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.105.164 with HTTP; Tue, 15 Aug 2017 08:51:24 -0700 (PDT) In-Reply-To: <87r2wdeqwr.fsf@jsievers.enova.com> References: <87r2wdeqwr.fsf@jsievers.enova.com> From: Scott Marlowe Date: Tue, 15 Aug 2017 09:51:24 -0600 Message-ID: Subject: Re: Odd sudden performance degradation related to temp object churn To: Jerry Sievers Cc: Jeremy Finzel , 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 4:16 PM, Jerry Sievers wrote: > Scott Marlowe writes: > >> You do know that temp tables go into the default temp table space, >> just like sorts, right? > > Not so. > > This system has no defined temp_tablespace however spillage due to > sorting/hashing that exceeds work_mem goes to base/pgsql_tmp which we > have symlinked out to a local SSD drive. Which is also where temp tables are created. -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance