Re: Problem getting sql statement logging to work
| От | David Klugmann |
|---|---|
| Тема | Re: Problem getting sql statement logging to work |
| Дата | |
| Msg-id | BAY104-F42886A7540168DC9ECBBB0B2850@phx.gbl обсуждение исходный текст |
| Ответ на | Re: Problem getting sql statement logging to work (Michael Fuhr <mike@fuhr.org>) |
| Список | pgsql-general |
Michael Many thanks. Configuring the syslog.conf and using logger to check it was working did the trick. Previously I had no local0 entries in the syslog.conf which was my problem. David >From: Michael Fuhr <mike@fuhr.org> >To: David Klugmann <dklugmann@hotmail.com> >CC: pgsql-general@postgresql.org >Subject: Re: [GENERAL] Problem getting sql statement logging to work >Date: Tue, 18 Jan 2005 09:51:27 -0700 > >On Tue, Jan 18, 2005 at 03:05:34PM +0000, David Klugmann wrote: > > > > I have the following entries in my postgresql.conf file yet it doesn't >seem > > to log anything. > >Did you restart the backend after modifying postgresql.conf? > > > syslog_facility = 'LOCAL0' > >Have you configured /etc/syslog.conf to send local0 messages anywhere? >You might need to add an appropriate line to /etc/syslog.conf, touch >the desired log file if it doesn't already exist, and send a HUP >signal to syslogd. > >You can test your syslog configuration with the "logger" program. >I think log_statement sends messages to the LOG_INFO syslog level, >so run the following command from the shell prompt and see if the >message gets logged: > >logger -p local0.info "test 1 to local0.info" > >Verify that your syslog configuration is working, make sure you've >restarted the PostgreSQL backend so it knows about the configuration >changes, and try again. > >-- >Michael Fuhr >http://www.fuhr.org/~mfuhr/
В списке pgsql-general по дате отправления: