Re: pgsql: Create a GUC parameter temp_tablespacesthat allows selection of

"Simon Riggs" <simon@2ndquadrant.com> writes:
> One of the main reasons for the implementation was to allow larger
> queries to work faster by utilising multiple temp tablespaces for the
> same query.

> The original ideal implementation was to use round-robin/cyclic
> selection, which allows much better usage in the above case.

Really?  What if multiple backends are all hitting the same tablespaces
in the same order?  A random selection seems much less likely to risk
having any self-synchronizing behavior.

            regards, tom lane