From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rick Otten <rottenwindfish@gmail.com>
Cc: pgsql-performa. <pgsql-performance@postgresql.org>
Subject: Re: blending fast and temp space volumes
Date: Wed, 21 Feb 2018 11:04:00 -0500
Message-ID: <11881.1519229040@sss.pgh.pa.us> (raw)
In-Reply-To: <CAMAYy4JeVqeNFSRuYWT5PZVUdxoidQrfHXX7DHE6N-nmu44WQg@mail.gmail.com>
References: <CAMAYy4JeVqeNFSRuYWT5PZVUdxoidQrfHXX7DHE6N-nmu44WQg@mail.gmail.com>
Rick Otten <rottenwindfish@gmail.com> writes:
> At the moment it seems like when multiple temp spaces are available, the
> temp spaces are chosen in a 'round robin' or perhaps 'random' fashion. Is
> that true?
Yes, see fd.c's SetTempTablespaces and GetNextTempTableSpace.
There's no concept of different temp spaces having different performance
characteristics, and anyway we don't really have enough info to make
accurate predictions of temp space consumption. So it's hard to see the
planner doing this for you automagically.
regards, tom lane
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: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, rottenwindfish@gmail.com
Subject: Re: blending fast and temp space volumes
In-Reply-To: <11881.1519229040@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox