From: | "Jaime Casanova" <systemguards(at)gmail(dot)com> |
---|---|
To: | "Peter Eisentraut" <peter_e(at)gmx(dot)net> |
Cc: | pgsql-patches(at)postgresql(dot)org, "Bruce Momjian" <bruce(at)momjian(dot)us> |
Subject: | Re: [WIP] GUC for temp_tablespaces |
Date: | 2007-05-09 00:21:06 |
Message-ID: | c2d9e70e0705081721s1f3bca5cy3ac38fdb81916fc1@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
On 5/8/07, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> Am Samstag, 5. Mai 2007 16:40 schrieb Jaime Casanova:
> > On 5/5/07, Bruce Momjian <bruce(at)momjian(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-05-09 00:52:20 | Re: updated WIP: arrays of composites |
Previous Message | Alvaro Herrera | 2007-05-08 20:53:05 | Re: [PATCHES] Patch: Allocation of "kind" codes for spatial type. |