Skip site navigation (1) Skip section navigation (2)

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Create a GUC parameter temp_tablespacesthat allows selection of
Date: 2007-06-04 18:41:14
Message-ID: 22765.1180982474@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
"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

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2007-06-04 19:12:44
Subject: Re: pgsql: Create a GUC parametertemp_tablespacesthat allows selection of
Previous:From: Simon RiggsDate: 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 RiggsDate: 2007-06-04 19:12:44
Subject: Re: pgsql: Create a GUC parametertemp_tablespacesthat allows selection of
Previous:From: Simon RiggsDate: 2007-06-04 18:35:28
Subject: Re: pgsql: Create a GUC parameter temp_tablespacesthat allows selection of

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group