Re: [PERFORM] Odd sudden performance degradation related to tempobject churn - Mailing list pgsql-performance

From Scott Marlowe
Subject Re: [PERFORM] Odd sudden performance degradation related to tempobject churn
Date
Msg-id CAOR=d=21SerRrRzFcUh6yGkVXNyzmT79y7L9pM9tq6Koc+-phg@mail.gmail.com
Whole thread Raw
In response to Re: [PERFORM] Odd sudden performance degradation related to temp object churn  (Jerry Sievers <gsievers19@comcast.net>)
Responses Re: [PERFORM] Odd sudden performance degradation related to tempobject churn  (Jeremy Finzel <finzelj@gmail.com>)
List pgsql-performance
On Mon, Aug 14, 2017 at 4:16 PM, Jerry Sievers <gsievers19@comcast.net> wrote:
> Scott Marlowe <scott.marlowe@gmail.com> 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.


pgsql-performance by date:

Previous
From: Mariel Cherkassky
Date:
Subject: Re: [PERFORM] performance problem on big tables
Next
From: Jeremy Finzel
Date:
Subject: Re: [PERFORM] Odd sudden performance degradation related to tempobject churn