Re: [WIP] GUC for temp_tablespaces - Mailing list pgsql-patches

From Jaime Casanova
Subject Re: [WIP] GUC for temp_tablespaces
Date
Msg-id c2d9e70e0705081721s1f3bca5cy3ac38fdb81916fc1@mail.gmail.com
Whole thread Raw
In response to Re: [WIP] GUC for temp_tablespaces  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [WIP] GUC for temp_tablespaces  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-patches
On 5/8/07, Peter Eisentraut <peter_e@gmx.net> wrote:
> Am Samstag, 5. Mai 2007 16:40 schrieb Jaime Casanova:
> > On 5/5/07, Bruce Momjian <bruce@momjian.us> wrote:
> > > Your patch has been added to the PostgreSQL unapplied patches list at:
> >
> > This is final version of the patch (i hope), at least it fixes the
> > problem i had yesterday.
>
> What I have been missing all along in these patches is an explanation for what
> it means to list multiple temporary tablespaces.  Are they used in order, or
> the first one that exists, or what?
>

http://archives.postgresql.org/pgsql-hackers/2007-01/msg00531.php
http://archives.postgresql.org/pgsql-patches/2007-01/msg00282.php

in src/backend/commands/tablespace.c:assign_temp_tablespaces():

   /*
     * Select the first tablespace to use
     */
    Assert(num_temp_tablespaces >= 0);
    if (num_temp_tablespaces != 0)
        next_temp_tablespace = MyProcPid % num_temp_tablespaces;


--
regards,
Jaime Casanova

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs and the universe trying
to produce bigger and better idiots.
So far, the universe is winning."
                                       Richard Cook

pgsql-patches by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] Patch: Allocation of "kind" codes for spatial type.
Next
From: Andrew Dunstan
Date:
Subject: Re: updated WIP: arrays of composites