| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jaime Casanova" <systemguards(at)gmail(dot)com> |
| Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Create a GUC parametertemp_tablespacesthat allows selection of |
| Date: | 2007-06-07 15:44:15 |
| Message-ID: | 11955.1181231055@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
"Jaime Casanova" <systemguards(at)gmail(dot)com> writes:
> On 6/4/07, 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.
> ok. are you doing this? or can i prepare a patch that implements this?
> i guess we can allocate the memory for the list in TopTransactionContext.
I'll work on it ... I want to rejigger the API between fd.c and
tablespace.c anyway. (fd.c still shouldn't be calling tablespace.c ...)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User H-saito | 2007-06-07 16:08:12 | pgsnmpd - pgsnmpd: Important publication. |
| Previous Message | User H-saito | 2007-06-07 15:25:33 | pgsnmpd - pgsnmpd: Note: about SrvLimitedResource. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2007-06-07 15:50:36 | Re: Autovacuum launcher doesn't notice death of postmaster immediately |
| Previous Message | Tom Lane | 2007-06-07 15:41:56 | Re: Vacuuming anything zeroes shared table stats |