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.
HTH
Darren Ferguson
On Tue, 11 Jun 2002, Chris Gamache wrote:
> Some of my carefully throught out, and painstakingly graded SQL inserts (or
> updates) are failing intermittantly because I guess I didn't grade hard enough!
> :)
>
> I'm getting ERROR: messages on the console (and rightly so!) ... My question
> is, how can I find out what the text of the failed query would be. That would
> give me a better clue as to where my code fails. It would also take a lot less
> time going through the code SQL statement by SQL statement to find the guilty
> one.
>
> I compiled --without-syslog to eek the last bit of performance out of
> PostgreSQL. I have no problem recompiling with more feedback detail enabled to
> resolve the problem. I just need a clue on where to start looking. The whole
> logging part of PostgreSQL is still magical to me.
>
> CG
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
