I wrote:
> However, accumulation of zillions of gmon.out files is definitely a
> downside of the approach; one that I've noticed myself. I've also
> noticed that it takes a heck of a long time to rm -rf $PGDATA once
> you've built up a few tens of thousands of gprof subdirectories. What's
> worse
You see, I'm not a trained developer, I'm just a dumb psychologist,
sometimes poking around w/ things I don't fully understand -- learning by
doing, or die trying ;-) Give me at least three years...
Seriously now, I didn't even think about possible downsides of
--enable-profiling, I just thought
J=?ISO-8859-1?B?9g==?=rg Beyer <[EMAIL PROTECTED]> writes:
> Attached is the log with the "du" output, one block for the build directory,
> one for the installation directory, and one for the 8.3-cluster. Some
> comments are added.
> I suspect gprof to be the culprit, everything gprof related is i
J=?ISO-8859-1?B?9g==?=rg Beyer <[EMAIL PROTECTED]> writes:
> I generally run make check, and that consumes some extra disk space, of
> course. While versions 8.1 and 8.2 were quite happy with a total of
> approximately 280-300 MB of free disk space for the build, 8.3 beta 2
> consumes *up to 1.6 Gi
Hello.
I compiled and installed PostgreSQL 8.3 beta 2 on OS X 10.4.10 these days,
and noticed a minor issue that may lead to some problems, occasionally.
I generally run make check, and that consumes some extra disk space, of
course. While versions 8.1 and 8.2 were quite happy with a total of
ap
