From: | "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "Bill Moran" <wmoran(at)collaborativefusion(dot)com>, pgsql-patches(at)postgresql(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] [PATCHES] Patch to log usage of temporary files |
Date: | 2007-01-12 19:48:17 |
Message-ID: | 1d4e0c10701121148x47efed86h39c27622cf97e78a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On 1/12/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> writes:
> > That's not what I had in mind. I was asking if the text of the query
> > was available when logging the temp file usage. If so it could be good
> > to add a DETAIL line with it directly and systematically when logging
> > the temp file usage.
>
> (1) you could make that argument about *any* log message whatsoever.
Yes, probably. The fact is I can't figure out how I will use this
information if I don't know why the file was created but perhaps I
should just wait this release and see how I can use it in a production
environment.
> (2) there is already a generalized solution to this, it's called
> log_min_error_statement.
I didn't think of that when posting my message but Bruce seems to say
that we can't use it in this case.
--
Guillaume
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-01-12 19:50:54 | Re: [HACKERS] table partioning performance |
Previous Message | Guillaume Smet | 2007-01-12 19:43:04 | Re: [PATCHES] Patch to log usage of temporary files |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-01-12 19:59:20 | Re: [HACKERS] [PATCHES] Patch to log usage of temporary files |
Previous Message | Guillaume Smet | 2007-01-12 19:43:04 | Re: [PATCHES] Patch to log usage of temporary files |