Re: Patch - Debug builds without optimization

Alvaro Herrera <alvherre@commandprompt.com>

From: Alvaro Herrera <alvherre@commandprompt.com>
To: Greg Smith <greg@2ndquadrant.com>
Cc: Greg Stark <stark@mit.edu>, Tom Lane <tgl@sss.pgh.pa.us>, Rados?aw Smogura <rsmogura@softperience.eu>, PG Hackers <pgsql-hackers@postgresql.org>
Date: 2011-06-20T17:27:23Z
Lists: pgsql-hackers
Excerpts from Greg Smith's message of lun jun 20 00:25:08 -0400 2011:
> Greg Stark wrote:
> > I've always wondered what other people do to iterate quickly.
> 
> I'd have bet money you had an elisp program for this by now!

Yeah :-)

> The peg utility script I use makes a reinstall as simple as:
> 
> stop
> peg build

But you're building the entire server there, which was Tom's point --
you only need to build and reinstall the backend.

I have my own "runpg" utility which does a lot of these things too ...
The main difference (to Tom's approach) is that I don't use pg_ctl to
start/stop the server, because I always keep that running in a terminal,
which makes for easier debugging because the logs are always there and I
can ctrl-c it ...  Well I guess it's pretty much the same thing, because
Tom probably has a script to stop the server.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support