On Monday 20 July 2009 18:58:21 Greg Sabino Mullane wrote:
Perhaps, but I don't think you've quite overcome the 'log everything'
counter-argument.
#
Not everybody can afford a system with lots of raid arrays or dedicated logging
boxes. Many people log to the same disk. I do it in some
On Monday 20 July 2009 19:24:13 Bill Moran wrote:
It is not possible for us. Logging millions of statements take too much
time.
This is a ridiculous statement. In actual practice, full query logging
is 1/50 the amount of disk I/O as the actual database activity. If your
systems are so
Janning Vygen vy...@kicktipp.de writes:
On Monday 20 July 2009 19:24:13 Bill Moran wrote:
Have you benchmarked the load it creates under your workload?
Yes, it takes up to 15% of our workload in an average use case. But we have
peak times where we can not afford 15% lost for logging!
Well,
On Tuesday 21 July 2009 15:49:36 Tom Lane wrote:
Janning Vygen vy...@kicktipp.de writes:
On Monday 20 July 2009 19:24:13 Bill Moran wrote:
Have you benchmarked the load it creates under your workload?
Yes, it takes up to 15% of our workload in an average use case. But we
have peak times
Janning Vygen vy...@kicktipp.de writes:
On Tuesday 21 July 2009 15:49:36 Tom Lane wrote:
Well, you could turn it off during the peak times.
It affords a server restart which is not a good idea.
Changing logging options does not require a server restart.
regards, tom
On Mon, Jul 20, 2009 at 1:28 PM, Joshua D. Drakej...@commandprompt.com wrote:
On Mon, 2009-07-20 at 13:24 -0400, Bill Moran wrote:
In actual practice, full query logging
is 1/50 the amount of disk I/O as the actual database activity. If your
systems are so stressed that they can't handle
On Tuesday 21 July 2009 18:09:57 you wrote:
Janning Vygen vy...@kicktipp.de writes:
On Tuesday 21 July 2009 15:49:36 Tom Lane wrote:
Well, you could turn it off during the peak times.
It affords a server restart which is not a good idea.
Changing logging options does not require a
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
In my experience, I've found that enabling full logging for a short time
(perhaps a few hours) gathers enough data to run through tools like
pgFouine and
In response to Greg Sabino Mullane g...@turnstep.com:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
In my experience, I've found that enabling full logging for a short time
(perhaps a few hours)
On Mon, 2009-07-20 at 13:24 -0400, Bill Moran wrote:
In response to Greg Sabino Mullane g...@turnstep.com:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
In my experience, I've found that enabling
On Jul 20, 2009, at 10:24 AM, Bill Moran wrote:
In response to Greg Sabino Mullane g...@turnstep.com:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
In my experience, I've found that enabling full logging for a
short time
(perhaps a few hours) gathers enough data to run through
In response to Joshua D. Drake j...@commandprompt.com:
On Mon, 2009-07-20 at 13:24 -0400, Bill Moran wrote:
In response to Greg Sabino Mullane g...@turnstep.com:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On Mon, 2009-07-20 at 13:46 -0400, Bill Moran wrote:
In response to Joshua D. Drake j...@commandprompt.com:
It depends on the system. I have seen even big systems take a huge hit
by full logging due to transactional velocity.
Perhaps I'm just in a foul mood today, but I feel like people
hi,
http://archives.postgresql.org/pgsql-general/2009-03/msg00581.php
This was my suggestion about introducing a statment to get a sample of SQL
statements. Nobody answered yet. Why not? i think my suggestion would help a
lot. Or was it kind of stupid?
kind regards
Janning
--
Sent via
In response to Janning Vygen vy...@kicktipp.de:
hi,
http://archives.postgresql.org/pgsql-general/2009-03/msg00581.php
This was my suggestion about introducing a statment to get a sample of SQL
statements. Nobody answered yet. Why not? i think my suggestion would help a
lot. Or was it
hi,
thanks for your comments on this.
On Thursday 16 July 2009 15:05:58 you wrote:
In response to Janning Vygen vy...@kicktipp.de:
hi,
http://archives.postgresql.org/pgsql-general/2009-03/msg00581.php
This was my suggestion about introducing a statment to get a sample of
SQL
Hi,
we ran a large database on moderate hardware. Disks are usually the slowest
part so we do not log every statement. Sometimes we do and our IOwait and CPU
increases by 10%. too much for peak times!
it would be nice if you could say:
log_statement = sample
sample_rate = 100
you would
17 matches
Mail list logo
