--On Montag, Juni 04, 2007 15:34:14 -0400 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> Perhaps a reasonable compromise could work like this: at the first point
> in a transaction where a temp file is created, choose a random list
> element, and thereafter advance cyclically for the duration of that
> transaction. This ensures within-transaction spread-out while still
> having some randomness across backends.
Doing this on transaction-level looks pretty nice; The original code choose
the random element on backend startup (or every time you call SET).
Btw. i saw you've removed the random selection implemented by MyProcId %
num_temp_tablespaces. I liked this idea, because PID should be pretty
random on many OS?
In response to
pgsql-hackers by date
|Next:||From: Heikki Linnakangas||Date: 2007-06-05 15:25:10|
|Subject: Re: GIN, XLogInsert and MarkBufferDirty|
|Previous:||From: Tom Lane||Date: 2007-06-05 15:18:36|
|Subject: Re: [HACHERS] privilege check: column level only? |
pgsql-committers by date
|Next:||From: Jan Wieck||Date: 2007-06-05 20:00:42|
|Subject: pgsql: The session_replication_role actually can be changed at will |
|Previous:||From: Bernd Helmle||Date: 2007-06-05 15:14:30|
|Subject: Re: [COMMITTERS] pgsql: Create a GUC
parametertemp_tablespacesthat allows selection of |