On Fri, 27 Apr 2007, Jim Nasby wrote:
Yes, but how many data drives would you need to have to bottleneck on WAL?
Even if the entire database is memory resident you'd still have to write all
the pages out at some point, and it seems to me that you'd need a fair amount
of disk capacity the data
On Apr 27, 2007, at 4:58 AM, Greg Smith wrote:
On Thu, 26 Apr 2007, Zeugswetter Andreas ADI SD wrote:
I am not sure that shrinking per WAL record size (other than the full
page images), e.g. by only logging changed bytes and not whole
tuples,
would have a huge impact on OLTP tx/sec, since
Writing to a different area was considered in pg, but there were
more
negative issues than positive.
So imho pg_compresslog is the correct path forward. The current
discussion is only about whether we want a more complex
pg_compresslog
and no change to current WAL, or an increased WAL
On Thu, 26 Apr 2007, Zeugswetter Andreas ADI SD wrote:
I am not sure that shrinking per WAL record size (other than the full
page images), e.g. by only logging changed bytes and not whole tuples,
would have a huge impact on OLTP tx/sec, since the limiting factor is
IO's per second and not Mb
