| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2007-06-05 20:00:42 | pgsql: The session_replication_role actually can be changed at will |
| Previous Message | Bernd Helmle | 2007-06-05 15:14:30 | Re: [COMMITTERS] pgsql: Create a GUC parametertemp_tablespacesthat allows selection of |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-06-05 15:25:10 | Re: GIN, XLogInsert and MarkBufferDirty |
| Previous Message | Tom Lane | 2007-06-05 15:18:36 | Re: [HACHERS] privilege check: column level only? |