From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | "Jaime Casanova" <systemguards(at)gmail(dot)com> |
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 08:10:50 |
Message-ID: | 200705091010.50920.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Am Mittwoch, 9. Mai 2007 02:21 schrieb Jaime Casanova:
> > 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
Those are discussions of possible ideas, not an acceptable documentation of
this feature.
> in src/backend/commands/tablespace.c:assign_temp_tablespaces():
That also isn't an acceptable place to put feature documentation.
> /*
> * Select the first tablespace to use
> */
> Assert(num_temp_tablespaces >= 0);
> if (num_temp_tablespaces != 0)
> next_temp_tablespace = MyProcPid % num_temp_tablespaces;
What does this mean? Is there code that selects the second tablespace to use?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 2007-05-09 09:04:03 | Re: ECPG patch to use prepare for improved performance |
Previous Message | Andrew Dunstan | 2007-05-09 00:52:20 | Re: updated WIP: arrays of composites |