The solution is not as sexy as the one I was hoping for... :) I'm not one to
look a gift-horse in the mouth. Thank you for your responses, which were right
on target. I imagine I can combine the debug_print_query with the logging to a
postgres.log and just do a
tail -f postgres.log | grep -B1 ERROR:
and see where I'm going wrong!
CG
--- Darren Ferguson <darren@crystalballinc.com> wrote:
> Redirect the output to a logfile of your choice. There was a huge talk
> about this yesterday on the list.
>
> #!/bin/bash
> HOME=/usr/local/pgsql
> LOG=$HOME/logs/postgres.log
> USER=darren
>
> ulimit -SHc unlimited
> su $USER -c "nohup $HOME/bin/postmaster -D $HOME/db $@ >$LOG 2>&1
> </dev/null&"
>
> This script above is what i use to start the postmaster and as you can see
> i redirect the output to the file postgres.log. There are also different
> logging levels in the postgres.conf file that you can turn on.
>
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com