Re: pgsql: Create a GUC parameter temp_tablespacesthat allows selection of - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Create a GUC parameter temp_tablespacesthat allows selection of
Date
Msg-id 22765.1180982474@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Create a GUC parameter temp_tablespacesthat allows selection of  ("Simon Riggs" <simon@2ndquadrant.com>)
Responses Re: pgsql: Create a GUC parametertemp_tablespacesthat allows selection of  ("Simon Riggs" <simon@2ndquadrant.com>)
Re: pgsql: Create a GUC parameter temp_tablespacesthat allows selection of  (Bruce Momjian <bruce@momjian.us>)
List pgsql-committers
"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

pgsql-committers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: pgsql: Create a GUC parameter temp_tablespacesthat allows selection of
Next
From: "Simon Riggs"
Date:
Subject: Re: pgsql: Create a GUC parametertemp_tablespacesthat allows selection of