Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Greg Stark wrote:
> >> Actually the sort algorithm postgres uses would be much more efficient if it
> >> could get access to two or three locations guaranteed to be on different
> >> spindles.
>
> > Agreed, and I was going to mention
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Greg Stark wrote:
>> Actually the sort algorithm postgres uses would be much more efficient if it
>> could get access to two or three locations guaranteed to be on different
>> spindles.
> Agreed, and I was going to mention the idea of a round-robin allo
Greg Stark wrote:
>
> Tom Lane <[EMAIL PROTECTED]> writes:
>
> > On the whole I'm unconvinced that this is worth the trouble. One of the
> > reasons for allowing people to move databases around is to determine
> > where their temp files go.
>
> The one scenario I would expect to see is having
Tom Lane <[EMAIL PROTECTED]> writes:
> On the whole I'm unconvinced that this is worth the trouble. One of the
> reasons for allowing people to move databases around is to determine
> where their temp files go.
The one scenario I would expect to see is having the temp files on filesystem
all
On Sat, 2004-10-30 at 00:50, Tom Lane wrote:
> (1) What are the protection requirements for this variable?
I think it can be USERSET -- most commands let the user specify a
tablespace explicitly, and this is basically just another way of doing
that. The user executing the query will need CREATE pr
Neil Conway <[EMAIL PROTECTED]> writes:
> So I'd like to add a GUC variable called something like
> "scratch_tablespace". If undefined (the default), temporary files for
> sorting/etc. will be created in the current database's tablespace.
(1) What are the protection requirements for this variable?
So I'd like to add a GUC variable called something like
"scratch_tablespace". If undefined (the default), temporary files for
Should be called 'work_tablesapce' to match 'work_mem' :)
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands
I'd like to provide a way for DBAs to specify that the temporary files
needed to for sorting, holdable cursors and similar operations should be
created in a particular tablespace. (Right now these files are created
in the tablespace associated with the current database.)
Two ways to do this come t
