| From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Finding bottleneck |
| Date: | 2005-08-22 17:18:28 |
| Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB3417DD167@Herge.rcsinc.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> That seems quite peculiar; AFAICS the pgstat code shouldn't be any
> slower than before. At first I thought it might be because we'd
> increased PGSTAT_ACTIVITY_SIZE, but actually that happened before
> 8.0 release, so it shouldn't be a factor in this comparison.
Just FYI the last time I looked at stats was in the 8.0 beta period.
> Can anyone else confirm a larger penalty for stats_command_string in
> HEAD than in 8.0? A self-contained test case would be nice too.
looking into it.
Merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luke Lonergan | 2005-08-22 17:46:33 | Re: MemoryContextSwitchTo during table scan? |
| Previous Message | Tom Lane | 2005-08-22 15:41:40 | Re: MemoryContextSwitchTo during table scan? |