Re: Problem getting sql statement logging to work

From: Richard_D_Levine(at)raytheon(dot)com
To: "David Klugmann" <dklugmann(at)hotmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, pgsql-general-owner(at)postgresql(dot)org
Subject: Re: Problem getting sql statement logging to work
Date: 2005-01-18 16:07:13
Message-ID: OFA4F1BCD9.6992E05F-ON05256F8D.00587649@ftw.us.ray.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

The problem may be in your /etc/syslog.conf file. It directs different
classes of messages different places, and can direct them to another
machine.

Rick


"David Klugmann"
<dklugmann(at)hotmail(dot)com> To: pgsql-general(at)postgresql(dot)org
Sent by: cc:
pgsql-general-owner(at)pos Subject: [GENERAL] Problem getting sql statement logging to work
tgresql.org


01/18/2005 10:05 AM

Hi

I am trying to log my sql statements to the syslog file.

I have the following entries in my postgresql.conf file yet it doesn't seem

to log anything.

The OS is Solaris 9

I am looking at /var/adm/messages and can't see anything from Postgres and
I
have run lots of sql.

I saw one article on the web which suggested setting debug_print_query =
on.
Is this an alternative way of setting logging ?

Thanks for any help.

David Klugmann

# - Syslog -

syslog = 2 # range 0-2; 0=stdout; 1=both;
2=syslog
syslog_facility = 'LOCAL0'
syslog_ident = 'postgres'

# - When to Log -

#client_min_messages = notice # Values, in order of decreasing
detail:
# debug5, debug4,
debug3, debug2, debug1,
# log, info, notice,
warning, error

#log_min_messages = notice # Values, in order of decreasing
detail:
# debug5, debug4,
debug3, debug2, debug1,
# info, notice, warning,
error, log, fatal,
# panic

#log_error_verbosity = default # terse, default, or verbose messages

#log_min_error_statement = panic # Values in order of increasing severity:
# debug5, debug4,
debug3, debug2, debug1,
# info, notice,
warning, error, panic(off)

#log_min_duration_statement = -1 # Log all statements whose
# execution time exceeds
the value, in
# milliseconds. Zero
prints all queries.
# Minus-one disables.

#silent_mode = false # DO NOT USE without Syslog!

# - What to Log -

#debug_print_parse = false
#debug_print_rewritten = false
#debug_print_plan = false
#debug_pretty_print = false
#log_connections = false
#log_duration = false
#log_pid = false
log_statement = true
#log_timestamp = false
#log_hostname = false
#log_source_port = false

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Browse pgsql-general by date

  From Date Subject
Next Message Hans-Michael Stahl 2005-01-18 16:49:05 Re: ECPG Segfaulting on EXEC SQL connect
Previous Message Juan Jose Siles Salinas 2005-01-18 15:48:05 Error al Subir base de datos