If you are using syslog, you should pay attention to: # These are relevant when logging to syslog: #syslog_facility = 'LOCAL0' #syslog_ident = 'postgres'
and make certain that your syslog.conf is not just discarding the messages. I usually log to stderr and redirect it to a log directory that is used by postgresql. You can also check the serverlog file in the postgres data directory. Cheers, Ken On Sun, Aug 10, 2008 at 09:07:09PM +0300, Ibrahim Harrani wrote: > Hi Ken, > > Thanks for your help. But I could not able to enable slow query logging. > I set > > log_destination = 'syslog' > logging_collector = off # Enable capturing of stderr and csvlog > log_min_duration_statement = 50 # -1 is disabled, 0 logs all statements > > But there is no log in the /var/log/messages about slow queries. > Did I miss something? > > Thanks > > > On Sat, Aug 9, 2008 at 10:12 PM, Kenneth Marshall <[EMAIL PROTECTED]> wrote: > > On Sat, Aug 09, 2008 at 08:35:28PM +0300, Ibrahim Harrani wrote: > >> \> Good. > >> > > >> >> What about the PgSQLConnectionCache value? I set it 30.. > >> >> > >> > This value should be set to the number of simultaneous DSPAM checks that > >> > you plan to run. Are you using the dspam server daemon/dspamc? > >> I am using the dspam server at daemon mode > >> > > >> >> By the way, I recognized that, While I am training dspam, total > >> >> process time increases from 0.3-0.4 seconds to 5-10 seconds. > >> >> > >> > Do you mean that it takes 5-10 seconds per message? > >> Yes, It takes 5-10 seconds per message. > >> > >> > >> >What version of DSPAM did you say that you were using? > >> # dspam --version > >> > >> DSPAM Anti-Spam Suite CVS (agent/library) > >> > >> > Do you have slow query logging enabled? If not, turn it on and run > >> > "EXPLAIN ANALYZE query" for some > >> > typical slow queries. They should all be using indexes and not > >> > sequential scans. > >> No, I did not enable slow query logging, I will do and inform you. > >> > > Also, since you are running PostgreSQL 8.3 you can turn off synchronous > > commit. > > This should give you a nice performance boost as well, similar to turning > > off > > fsync but the DB is consistant and healthy if power is lost. You may lose an > > update, but the database will still be okay. > > > > Ken > > > !DSPAM:1011,489f3446150921742619702!
