Kevin Grittner wrote:
Anyway, I'm not sure whether your reply directly answers the point
I was raising -- peg doesn't do anything with the compiler
optimization flags under the covers, does it?
Not really. It does this:
PGDEBUG="--enable-cassert --enable-debug"
./configure --prefix=$PGINST/$PGPROJECT --enable-depend
--enable-thread-safety $PGDEBUG
Which are pretty standard options. The idea is that you'd use the
default normally, then just set PGDEBUG=" " for a non-debug build--or to
otherwise change the configure flags but still get things done
automatically for you. If it's set before the script starts, it doesn't
change it.
I did try to design things so that you could do any step in the
automated series manually and not have that screw things up. There's
hundreds of lines of code in there just for things like figuring out
whether configure has been run or not yet when it decides you need to
build, so it can try to do the right thing in either case. My hope was
that anyone who tried peg out would find it a net positive time savings
after a single use, glad to hear I accomplished that in your case.
--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
g...@2ndquadrant.com www.2ndQuadrant.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
