"Simon Riggs" <simon(at)2ndquadrant(dot)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

In response to

• Re: pgsql: Create a GUC parameter temp_tablespacesthat allows selection of at 2007-06-04 18:35:28 from Simon Riggs

Responses

• Re: pgsql: Create a GUC parametertemp_tablespacesthat allows selection of at 2007-06-04 19:12:44 from Simon Riggs
• Re: pgsql: Create a GUC parameter temp_tablespacesthat allows selection of at 2007-06-05 03:46:08 from Bruce Momjian

pgsql-hackers by date

Next:	From: Simon Riggs	Date: 2007-06-04 19:12:44
	Subject: Re: pgsql: Create a GUC parametertemp_tablespacesthat allows selection of
Previous:	From: Simon Riggs	Date: 2007-06-04 18:35:28
	Subject: Re: pgsql: Create a GUC parameter temp_tablespacesthat allows selection of

pgsql-committers by date

Next:	From: Simon Riggs	Date: 2007-06-04 19:12:44
	Subject: Re: pgsql: Create a GUC parametertemp_tablespacesthat allows selection of
Previous:	From: Simon Riggs	Date: 2007-06-04 18:35:28
	Subject: Re: pgsql: Create a GUC parameter temp_tablespacesthat allows selection of