Re: Logging/Debugging - Mailing list pgsql-general

From Tielman J de Villiers
Subject Re: Logging/Debugging
Date
Msg-id E1F206EC93DCD4119A05009027A41359064AE9@sbssvr.bondnet.co.za
Whole thread Raw
In response to Logging/Debugging  (Tielman J de Villiers <tjdevil@bondnet.co.za>)
List pgsql-general
Colm

Thank you very much.

This in postgresql.conf gives me exactly what I wanted:

log_connections = true
log_timestamp = true
log_pid = true
debug_level = 2
debug_print_query = true


THOUGH I would prefer a further option to only display the
query/date/pid/db_name

(the rest are completely "lost' for an entry level user like me)

Logging the above information helps me to check when certain web pages take
exceptional strain, and when/if I should cache them to relive the strain ...



Tielman J de Villiers
BondNet Pty Ltd

-----Original Message-----
From: Colm McCartan [mailto:colmm@owl.co.uk]
Sent: Monday, December 10, 2001 11:23 AM
To: Tielman J de Villiers
Subject: Re: [GENERAL] Logging/Debugging




Tielman J de Villiers wrote:

> Hi,
>
> I went through the man pages for postmaster, as well as "pg_ctl
> --help" for options to log a date/time stamp in the "serverlog" but
> could not find it. It was also not clear to me what debug levels are
> available (other than 1) and what they log. How would I go about this?


Tielman,

you'll find lots of basic information on this in the idocs at:

http://www.postgresql.org/idocs/index.php?runtime-config.html

However, I too would like a little more detail as to what each of the
debugging levels signifies - does anyone have any more detailed info?

Thanks,

colm

pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Timing a query
Next
From: Antonio Fiol Bonnín
Date:
Subject: Analyzer for postgresql.log