| From: | Bill Moran <wmoran(at)collaborativefusion(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Advice on selecting good values for work_mem? |
| Date: | 2006-12-18 21:18:05 |
| Message-ID: | 20061218161805.04699b10.wmoran@collaborativefusion.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
In response to Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Bill Moran <wmoran(at)collaborativefusion(dot)com> writes:
> > Does the creation of a temp file trigger any logging?
>
> No; but it wouldn't be hard to add some if you wanted. I'd do it at
> deletion, not creation, so you could log the size the file reached.
> See FileClose() in src/backend/storage/file/fd.c.
Is this along the lines of what you were thinking? Is this acceptable
to get pulled into the tree (maintaining local patches sucks ;) I've
only been using this patch a day and I'm already giddy about how much
it helps tuning work memory sizes ...
--
Bill Moran
Collaborative Fusion Inc.
| Attachment | Content-Type | Size |
|---|---|---|
| fd.diff | text/x-diff | 766 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bill Moran | 2006-12-18 21:43:05 | Re: Advice on selecting good values for work_mem? |
| Previous Message | Tom Lane | 2006-12-18 18:00:55 | Re: Insertion to temp table deteriorating over time |