Re: [HACKERS] log_duration and log_statement

2006-03-14 Thread Jim C. Nasby
On Tue, Mar 14, 2006 at 08:50:22AM +, Simon Riggs wrote: > Is the issue that the log volume is too high? We might be able to look > at ways to reduce/compress the log volume for duration/statement > logging. ISTM that for performance analysis there's probably a better alternative than just dum

Re: [HACKERS] log_duration and log_statement

2006-03-14 Thread Guillaume Smet
Simon, On 3/14/06, Simon Riggs <[EMAIL PROTECTED]> wrote: > Thanks very much for writing pgFouine. We've been doing our best to > support generation of useful logs for performance analysis, so please > feel free to ask for anything you see a need for. OK. Thanks. I should write something clear ab

Re: [HACKERS] log_duration and log_statement

2006-03-14 Thread Guillaume Smet
On 3/14/06, Qingqing Zhou <[EMAIL PROTECTED]> wrote: > I guess they should read as "2006" :-) Sure. Will fix it this evening. Thanks. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings

Re: [HACKERS] log_duration and log_statement

2006-03-14 Thread Qingqing Zhou
""Guillaume Smet"" <[EMAIL PROTECTED]> wrote > > Here are some background information to explain our issue and request. On a separate issue, seems in pgfouine homepage a typo is there for a while: What's New 2005-02-11 - pgFouine 0.4.99 released ... 2005-01-10 - pgFouine 0.2.1 released ... I gu

Re: [HACKERS] log_duration and log_statement

2006-03-14 Thread Simon Riggs
On Mon, 2006-03-13 at 23:40 +0100, Guillaume Smet wrote: > Here are some background information to explain our issue and request. > We are currently planning a migration from PostgreSQL 7.4 to > PostgreSQL 8.1. We work on a medium sized database (2GB) with a rather > important activity (12 million

[HACKERS] log_duration and log_statement

2006-03-13 Thread Guillaume Smet
Hello, Here are some background information to explain our issue and request. We are currently planning a migration from PostgreSQL 7.4 to PostgreSQL 8.1. We work on a medium sized database (2GB) with a rather important activity (12 millions queries a day with peaks up to 1000 queries/s). We are a