Re: PostgreSQL 9.2 Logging - Mailing list pgsql-general

From Luca Ferrari
Subject Re: PostgreSQL 9.2 Logging
Date
Msg-id CAKoxK+6GVY-0HnyGO8uR+sKk0E7kNPJ+KwJmwt9KL4Gz8de4eA@mail.gmail.com
Whole thread Raw
In response to PostgreSQL 9.2 Logging  ("carlosinfl ." <carlos.mennens@gmail.com>)
List pgsql-general
On Wed, Aug 21, 2013 at 9:55 PM, carlosinfl . <carlos.mennens@gmail.com> wrote:

> #debug_print_parse = off
> #debug_print_rewritten = off
> #debug_print_plan = off
> #debug_pretty_print = on
> #log_checkpoints = off
> #log_connections = off
> #log_disconnections = off
>

The debug_* will log, well, debug information (e.g., the query being
rewritten and the query tree).
The log_*connections can be useful to see who is using the system.

I would also evaluate:
#log_min_messages = warning


Also
#log_statement = 'none'

that can be used to log all commands (query and utility), only ddl
(e.g., alter table),  and so on.

Hope this helps.

Luca


pgsql-general by date:

Previous
From: Luca Ferrari
Date:
Subject: Re: How to know detailed information about HOT(Heap-Only Tuples)?
Next
From: Michael Paquier
Date:
Subject: Re: Bug in psql (\dd query)