| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mike Roest <mike(dot)roest(at)replicon(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_dump incredibly slow dumping a single schema from a large db |
| Date: | 2012-03-30 17:30:26 |
| Message-ID: | 24744.1333128626@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Mike Roest <mike(dot)roest(at)replicon(dot)com> writes:
> Ok I just realized that's probably not going to be much help :)
gmon.out would be of no value to anybody else anyway --- making sense of
it requires the exact executable you took the measurements with.
> 0.00 0.00 0.00 5 0.00 0.00 canonicalize_path
> 0.00 0.00 0.00 5 0.00 0.00
> trim_trailing_separator
> 0.00 0.00 0.00 3 0.00 0.00 strlcpy
Ugh. There are some platforms on which gprof is busted to various
degrees; you may have one. What platform is this exactly?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Roest | 2012-03-30 17:33:38 | Re: pg_dump incredibly slow dumping a single schema from a large db |
| Previous Message | Mike Roest | 2012-03-30 17:17:06 | Re: pg_dump incredibly slow dumping a single schema from a large db |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Roest | 2012-03-30 17:33:38 | Re: pg_dump incredibly slow dumping a single schema from a large db |
| Previous Message | Greg Stark | 2012-03-30 17:30:05 | Re: tracking context switches with perf record |