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

Re: [COMMITTERS] pgsql: Create a GUC parametertemp_tablespacesthat allows selection of

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Create a GUC parametertemp_tablespacesthat allows selection of
Date: 2007-06-05 15:20:10
Message-ID: FCE033441D366B51FA1DBF1A@imhotep.credativ.de (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
--On Montag, Juni 04, 2007 15:34:14 -0400 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 
wrote:

> 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?

-- 
  Thanks

                    Bernd

In response to

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2007-06-05 15:25:10
Subject: Re: GIN, XLogInsert and MarkBufferDirty
Previous:From: Tom LaneDate: 2007-06-05 15:18:36
Subject: Re: [HACHERS] privilege check: column level only?

pgsql-committers by date

Next:From: Jan WieckDate: 2007-06-05 20:00:42
Subject: pgsql: The session_replication_role actually can be changed at will
Previous:From: Bernd HelmleDate: 2007-06-05 15:14:30
Subject: Re: [COMMITTERS] pgsql: Create a GUC parametertemp_tablespacesthat allows selection of

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