| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | a_ogawa(at)hi-ho(dot)ne(dot)jp |
| Cc: | pgsql-patches(at)postgresql(dot)org, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Subject: | Re: doc/FAQ_DEV: about profile |
| Date: | 2005-09-18 04:04:21 |
| Message-ID: | 11509.1127016261@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
a_ogawa(at)hi-ho(dot)ne(dot)jp writes:
> Though there is a description for the profile in doc/FAQ_DEV:
>> You can also compile with profiling to see what functions are taking
>> execution time. The backend profile files will be deposited in the
>> pgsql/data/base/dbname directory.
> The backend profile files is deposited in the pgsql/data directory
> on my linux now. I think that we should correct doc/FAQ_DEV.
Right. Also, if there's anyplace we say that core-dump files would go
into the per-database subdirectories, that's not true anymore either.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2005-09-19 15:05:16 | Re: Per-table freeze limit proposal |
| Previous Message | a_ogawa | 2005-09-18 01:46:52 | doc/FAQ_DEV: about profile |