On Oct 27, 2004, at 0:57, TTK Ciar wrote:
At a guess, it looks like the data set is being buffered in its
entirety by psql, before any data is written to the output file,
which is surprising. I would have expected it to grab data as it
appeared on the socket from postmaster and write it to disk.
Hello!
My name is TTK, and I'm a software engineer at the Internet Archive's
Data Repository department. We have recently started using postgresql
for a couple of projects (we have historically been a MySQL outfit),
and today my co-worker noticed psql eating memory like mad when invoked
wit
Tom Lane wrote:
It could be that I'm all wet and there is no relationship between the
cache line thrashing and the seemingly excessive BufMgrLock contention.
Is it important? The fix is identical in both cases: per-bucket locks
for the hash table and a buffer aging strategy that doesn't need on
Turns out the man page of vmstat in procps was changed on Oct 8 2002:
http://cvs.sourceforge.net/viewcvs.py/procps/procps/vmstat.8?r1=1.1&r2=1.2
in reaction to a debian bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=157935
--
Markus Bertheau <[EMAIL PROTECTED]>
